search

k8ssandra / cloud-readiness

Cloud readiness verifications for K8ssandra.
Apache License 2.0
1 stars 1 forks source link

Data-plane k8ssandra-operator designation #13

Closed jeffbanks closed 2 years ago

jeffbanks commented 2 years ago

Data-plane k8ssandra operator has K8SSANDRA_CONTROL_PLANE set to true in current version being used 0.5.0

k8ssandra-operator      bootz           1               2022-02-11 14:44:28.2038539 -0600 CST   deployed        k8ssandra-operator-0.35.0       0.4.0
Name:         k8ssandra-operator-85b9659c56-dlwc4
Namespace:    bootz
Priority:     0
Node:         gke-dev-bootz102-dev-bootz102-node-po-63bd73fd-c37f/10.0.0.8
Start Time:   Fri, 11 Feb 2022 14:44:34 -0600
Labels:       app.kubernetes.io/instance=k8ssandra-operator
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=k8ssandra-operator
              app.kubernetes.io/part-of=k8ssandra-k8ssandra-operator-bootz
              control-plane=k8ssandra-operator
              helm.sh/chart=k8ssandra-operator-0.35.0
              pod-template-hash=85b9659c56
Annotations:  <none>
Status:       Running
IP:           10.76.1.7
IPs:
  IP:           10.76.1.7
Controlled By:  ReplicaSet/k8ssandra-operator-85b9659c56
Containers:
  k8ssandra-operator:
    Container ID:  containerd://70e933eb545887ada5114fded5f6ec3249d66e3e86d4b5aab46e5f77f48d95e8
    Image:         docker.io/k8ssandra/k8ssandra-operator:v0.4.0
    Image ID:      docker.io/k8ssandra/k8ssandra-operator@sha256:f9868cd7c951f151ae3b4eb8f4de7b7cd26f0fe18e58ed17f2ce8c7c1f431682
    Port:          <none>
    Host Port:     <none>
    Command:
      /manager
    State:          Running
      Started:      Fri, 11 Feb 2022 14:44:42 -0600
    Last State:     Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 11 Feb 2022 14:44:35 -0600
      Finished:     Fri, 11 Feb 2022 14:44:41 -0600
    Ready:          True
    Restart Count:  1
    Liveness:       http-get http://:8081/healthz delay=15s timeout=1s period=20s #success=1 #failure=3
    Readiness:      http-get http://:8081/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment:
      WATCH_NAMESPACE:          bootz (v1:metadata.namespace)
      K8SSANDRA_CONTROL_PLANE:  true
    Mounts:
      /controller_manager_config.yaml from manager-config (rw,path="controller_manager_config.yaml")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-r2ccq (ro)

Expecting this to be set to false for the deployments on data-plane.

Unclear if this the version being used of the k8ssandra-operator or the cloud-readiness test logic. Both Helm and KubeConfig are setting the environment variable.

jeffbanks commented 2 years ago

cloud-readiness test model includes optional labels to be applied for identification of control-plane and data-plane designation, scoped to a unique context. This can be used for K8SSANDRA_CONTROL_PLANE environment settings as needed. It was determined there was no need to control this setting as part of the test framework.