https://github.com/cloud-pak-gitops/instana-gitops/blob/main/config/crossplane-provider/templates/init/99-postsync-job.yaml

the provider config should bound to one instana instance but not provider

@jianh619

What steps did you take and what happened:

We need to update document to adding argocd CLI to create applications, so that the CICD or some test tools can leverage argocd CLI to do gitops.

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

need to check if crossplane and crossplane provider can be deployed together

We need to update this chart to enable deploy instana on k8s. We can install the operator and create the CR using GitOps

As we want to enable GitOps for everything, so here I think the cluster only need to have Argo CD, and Argo CD can help install crossplane, crossplane provider and Instana in sequence.

/cc @cloud-pak-gitops/cp4wiops-gitops-core

Test and update doc https://github.com/cloud-pak-gitops/instana-gitops/blob/main/docs/install-instana-with-ocp-gitops.md

We need to update this chart to enable deploy instana on k8s. We can install the operator and create the CR using GitOps

This is related to #3 , the. major difference is we need to run following CLI to fix some SCC issues on OCP, this is kind of hack for now, need to fix them soon.

oc adm policy add-scc-to-user anyuid -z instana-core -n instana-core
oc adm policy add-scc-to-user anyuid -z default -n instana-core
oc adm policy add-scc-to-user anyuid -z default -n instana-units

User Story

As a [developer/user/operator] I would like to [high level description] for [reasons]

Detailed Description

• Using GitOps to install Instana 211 https://www.instana.com/docs/releases/on_prem_k8s_notes/build_211/
• Using GitOps to upgrade from 209 to 211

[A clear and concise description of what you want to happen.]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]

https://github.com/cloud-pak-gitops/instana-gitops/blob/main/config/instana/templates/config.yaml#L4 is hardcoding the provider config name.

What did you expect to happen:

If multiple instana instances are deployed, each instance may have different provider config.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

What steps did you take and what happened:

when user use another name instead default instana-settings , it won't work . https://github.com/cloud-pak-gitops/instana-gitops/blob/main/config/instana/values.yaml#L8

What did you expect to happen:

User is able to customize the configmap name

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

@jianh619 @liyanwei93

Enable hybrid model for Instana: DB in VM and Instana Core/Units in Container.

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]

What did you expect to happen:

We should leverage the openshift operator hub to install crossplane.

We need to update the document to highlight this.

@cloud-pak-gitops/cp4wiops-gitops-core

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

https://github.com/cloud-pak-gitops/instana-gitops/tree/main/config/argocd-apps/all-in-one

After deploying instana on the Kind cluster, all pods run successfully. Logs of pod instana-k8s-kubeconfig-l28qr shows:

To access Instana UI, open https://instana-k8s-kubeconfig-l28qr in browser.
- username: [email protected]
- password: passw0rd

But can not access UI through https://instana-k8s-kubeconfig-l28qr or https://<hostname>.

Env:
Instana provider: 9.30.233.157
Kind cluster: 9.112.255.86

I was deploying crossplane provider in same namespace as crossplane and both in crossplane-system, after I delete the argocd application for crossplane provider, the crossplane core components are also deleted.

The crossplane core component should not be deleted.

/cc @cloud-pak-gitops/crossplane-gitops

There should be three apps, but only one app tile shown as below:

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
The two crossplane container are running as root , need specify scc policy

What did you expect to happen:
Crossplane app should deploy on ocp properly

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]

What did you expect to happen:

We need to make sure the provider config installed first, and then install instana instance.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

@jianh619 @liyanwei93 ^^

Test and update doc https://github.com/cloud-pak-gitops/instana-gitops/blob/main/docs/install-instana-with-k8s-gitops.md

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
Both Instana and cp4waiops gitops need install an infra app , which contains crossplane deployment , it will cause conflict that both infra-instana and infra-cp4waiops won't be synced at same time (either infra-instana synced or infra-cp4waiops synced ) . We will meet another issue during uninstall , there's no choice for user to uninstall just one infra app , it will delete all crossplane resources as well as providers .

What did you expect to happen:
Separate the crossplane(and providers) as an shared resources , they just deploy once . It also makes gitops on OCP/K8s has consistent experience (two ways to deploy crossplane ) .

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

User Story

As a [tech seller] I would like to [know how instana can report back to management] for [information]

Detailed Description

[see above]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

https://github.com/cloud-pak-gitops/instana-gitops/tree/main/instana-automatic#verify-installation

@jianh619 @liyanwei93

we need to provide a guidance for how to manage the release and make sure it can align with Instana release.

What steps did you take and what happened:

User need provide config such as kubeconfig/pullsecret/product settings etc , and store it by either secret or configmap in a namespace . It's not suitable to just use crossplane install namespace crossplane-system for following reasons:

• The crossplane installed namespace is different from OCP and k8s , gitops experience is un-consistent
• All these config are user data , it should be protected by user themselves( it may be deleted when uninstalling gitops tools)

What did you expect to happen:

Create an individual namespace to user to operate , it may not have to customize by user itself .

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Minikube/KIND version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):
• Instana version:
• Crossplane version:

@jianh619 @liyanwei93