Gitlab Environment DaemonSet Tracking
I have recently been experimenting with gitlab kubernetes deployments, via connecting a external k8s cluster, and using a ci/cd job to deploy to the cluster. The application which I am deploying is configured as a
DaemonSet, and it seems that the environments dashboard doesn't find the daemonset.
apiVersion: apps/v1 kind: DaemonSet metadata: name: my-app annotations: app.gitlab.com/app: "$CI_PROJECT_PATH_SLUG" app.gitlab.com/env: "$CI_ENVIRONMENT_SLUG" labels: k8s-app: my-app spec: selector: matchLabels: name: my-app template: metadata: labels: name: my-app spec: nodeSelector: my-app: enabled hostname: my-app containers: - name: client image: $CI_APPLICATION_REPOSITORY:$CI_APPLICATION_TAG imagePullPolicy: IfNotPresent resources: limits: cpu: 200m memory: 10Mi requests: cpu: 200m memory: 10Mi
The message I see in the environment dashboard is:
Kubernetes deployment not found To see deployment progress for your environments, make sure you are deploying to $KUBE_NAMESPACE and annotating with app.gitlab.com/app=$CI_PROJECT_PATH_SLUG and app.gitlab.com/env=$CI_ENVIRONMENT_SLUG.
My deploy job script deploys using the lines:
kubectl describe namespace "$KUBE_NAMESPACE" || kubectl create namespace "$KUBE_NAMESPACE" envsubst < my-app-ds.yaml | kubectl apply -n "$KUBE_NAMESPACE" -f -
Does this literally mean a kubernetes
Deployment object, or is it just referring to a kubernetes application deployment, wrapped in whatever controller you'd like?
Are DaemonSets supported?