es-operator | Kubernetes Operator for Elasticsearch | Continuous Deployment library

Please try following :

kubectl get ocivaultkeys operator-key-broken -o jsonpath='{.status.conditions[?(@.ansibleResult)].type}'

Expected output : Failure

jsonpath help

You set the configtree base path to /etc/secrets/. You volume mounted the secret value into the file /etc/secrets/postgres/HOST. Configtree converts the subdirectory path to a dot-separated prefix on the configuration property name, so the secret value is readable from configuration property name postgres.HOST.

container_import is the correct rule to import an existing image. However, all it does is import, it doesn't pull it from anywhere. I think you're looking for container_pull instead, which will pull an image from a repository and then automatically use container_import to translate it for other rules_docker rules.

To add a new layer, use container_image, with base set to the imported image and tars set to the additional files you want to add. Or, if you want to add things in other formats, see the docs for alternates to tars (like debs or files).

Putting it all together, something like this in your WORKSPACE:

Are you trying to delete a pod or the Stateful set itself?

Try to run:

As per your comments you are actually interessted in more of a cloud-native solution to operating a Jenkins, so here goes.

Since you already have a Kubernetes cluster and would like to use the Jenkins Kubernetes operator, then I would recommend you use the Jenkins Kubernetes Plugin for managing your workloads.

The Jenkins Kubernetes plugin enables you to run each of your pipelines in a separate Pod in your Kubernetes cluster, and once the required Service resources are setup, then the communication between master and slave pods is completely regulated by the plugin. I would recommend that you look into their documentation, which is quite good ( in comparison to other plugins ).

Now since you are also using the Jenkins Kubernetes operator you should know that the plugin is installed as one of the default plugins and is available as soon as your Jenkins instance is spun up. I would recommend you read through the Jenkins Kubernetes operator documentation to get a better grasp of what happens when that is running.

So now I will move onto your questions.

1. Do I've to set up a new instance of Jenkins before hand on my K8s cluster or kubernetes-operator does that for me ?

If you install the Jenkins Kubernetes operator via Helm chart, then no, you get a Jenkins master instance included. Otherwise if you install the controller into your cluster manually, then you will need to create a Jenkins CRD, which will create a Jenkins instance for you.

1. Looking to access the Jenkins instance under the domain : jenkins.mybusinessunit.myorg.com/jenkins

Use Ingress + Load Balancer + DNS Service or expose the Pod via NodePort. Note that exposing your master Pod via NodePort may require you to make your Jenkins Master instance publicly available ( and that may not be wise ).

1. Do I have to do any addtional configurations to enable master - slave set up.

Please refer to the documentation of Jenkins Kubernetes plugin and Jenkins Kubernetes operator. All details are provided there, but configuration is rather minimal.

1. Does kubernetes-operator provides a feature to support CI/CD model like Jenkins X

No. The Jenkins Kubernetes operator is there only to manage your Jenkins instance and backups in immutable fashion. Jenkins X can be used in combination with Jenkins, but neither replaces the other completely.

The error you provided says what is wrong:

I think you could be interested into using local type of volumes. It works, like this:

First, you create a storage class for the local volumes. Something like the following:

They don't. Not directly, anyways. Communication on Kubernetes occurs purely through YAML files.

For example, if your application requires access to a database, you should install an operator for Postgresql, create a PostgreSQLCluster CR Object, and pull credentials from it once it's setup.

However, this isn't a practical solution in the long term, because Operators should be able to update automatically and without interaction. You are also not allowed to install older versions. To name names, the Crunchy Postgres Operator actually goes through many breaking changes with every update. If you were relying on them maintaining their CRD format, you made your architecture a brittle one.

A few exceptions do exist. Operators for products like Tekton Pipelines and Argo Pipelines are very stable and unlikely to change by design, and it's perfectly OK to depend on these.

Speaking purely towards the best practices, you are supposed to be able to migrate from older to newer versions of your CRD API using webhooks, though it isn't clear that any Operator implementations actually do this. Still, as of writing this post, there are no Operators on OperatorHub.io which rely on other Operators (Feb 16, 2021). Reader, you will be the first.

If you wanted to do so anyway, chances are the Operator you want to depend on is available on the Go package repository. You can just go get them and use their CRD API types natively in your code, which should make it very easy to keep up to date with the API.

Technically, the Operator you want to depend on could implement a REST API in their manager, and expose it as a service. I seriously doubt anybody will ever do this. It doesn't seem smart to poke holes into the Kubernetes design philosophy and open up attack vectors.

you can use this command to update the deployment image of mongo