Kubernetes Generic Check

[moshloop]

kubernetesResource:
        
    - name: deploy a pod and check that it is accessible via ingress
       staticResources: # are deleted when the canary is deleted
         - Ingress spec
         - svc spec
       resources: # deleted after the check
         - A pod spec
       waitForReady: true # wait for resources to be ready before running checks
       timeout: 10m
       testResults: # extract test results from running pods
            -  path: /test/junit.xml
                type: junit # default
                pod:
                    name: {{.resources[0].metadata.name
                    # selector:
       checks:
         - http:
             url: {{.staticResources[0].ingress.spec.hostname }}             

Successor to pod, namespace jmeter and junit checks

Work started here: #368

[k8sexperiment]

It would be very cool to have a full, flexible Kubernetes check specification, especially for cloud environments:

Create a pod, and once it's ready, you can check:

External-dns/Ingress/Cert-manager via Ingress manifest: Once the Ingress is created, you can verify that a certificate was created for the host and a record was created via external-dns. Hence, if TLS ingress is successful, the URL check should return a 200/green status.

ImagePull: This is simple; if the pod is created and pulled using a custom registry, it should be working properly.

HPA/Keda: Utilizing k6 load test, check if the pod is scaling based on metrics.

WorkloadIdentity: Suppose correct credentials are added as annotations/labels to the pod's ServiceAccount and pod.spec.template. In that case, you might want to test access to the Cloud resources from the pod. You can mount secrets from a cloud vault or push/pull files from S3/GCS/Azure StorageAccount, etc. Again, this might be related to Kubernetes resources specification.

PVC Volume attached: Test CSI to ensure proper functionality.