k8s-deploy | GitHub Action for deploying to Kubernetes clusters | Continous Integration library

To give a pod control over something in Kubernetes you need at least four things:

1. Create or select existing Role/ClusterRole (you picked administer-cluster, which rules are unknown to me).
2. Create or select existing ServiceAccount (you created k8s-deployer in namespace tooling).
3. Put the two together with RoleBinding/ClusterRoleBinding.
4. Assign the ServiceAccount to a pod.

Here's an example that can manage namespaces:

The secret returned via API (kubectl get secret ...) is a JSON-structure, where there:

If anyone comes across this problem in the future, make sure your ingress is properly configured. The error message suggests that its a misconfiguration with the ingress.

You can do it by installing elasticsearch using helm chart and modifying values.yaml. It allows you to modify elasticsearch.yaml.

You can enable xpack.security.enabled: true with following configuration:

I think you might have missed the step of installing CRD and the operator for ElasticSearch. Have you followed this step https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-eck.html?

Service, Pod, Deployment etc are Kubernetes native resources. Kubernetes provides a way to write custom resources also, using CRDs. Elasticsearch is one such example, so you have to define custom resource before using it for Kubernetes to understand that.

After some research, i found this solution:

You are creating a docker_build.txt file with the content of
echo "building app..."| tee -a build_result.txt but then you are changing the directory to /app and then you create another docker_build.txt and finally you build your artifact.

But you see your first docker_build.txt not with your ls command because your starting directory is not / but the a dynamic path provided by the CI_PROJECT_DIR predefined variable

Further all artifact defintions are also relativ to this path, therefore after moving your docker_build.txt command this should work:

Your Apache/WSGI server is doing the redirect. After the redirect to /, the client goes back to the ingress and the ingress doesn't know how to handle that so it will show you a 404

Your Apache/WSGI server is doing the redirect. After the redirect to /, the client goes back to the ingress and the ingress knows how to handle / and it all works great.

So both your ingress (which is running nginx) and Apache need to agree on the same path all the time. So you either use / on your ingress or you change your Apache configuration to also serve on /tascaty so that instead of redirecting to / it redirects to /tascaty.

Example of the latter: