Unable to deploy pulp-operator 1.0.0-alpha.1

Support
#1

When i try to deploy operator version 1.0.0-alpha.1, with the command:

make deploy

i get the error

/home/galaxy/pulp-operator/bin/kustomize build config/default | kubectl apply -f -
namespace/galaxy created
customresourcedefinition.apiextensions.k8s.io/pulpbackups.repo-manager.pulpproject.org created
customresourcedefinition.apiextensions.k8s.io/pulprestores.repo-manager.pulpproject.org created
customresourcedefinition.apiextensions.k8s.io/pulps.repo-manager.pulpproject.org created
serviceaccount/pulp-operator-controller-manager created
role.rbac.authorization.k8s.io/pulp-operator-leader-election-role created
role.rbac.authorization.k8s.io/pulp-operator-manager-role created
clusterrole.rbac.authorization.k8s.io/pulp-operator-manager-role created
clusterrole.rbac.authorization.k8s.io/pulp-operator-metrics-reader created
clusterrole.rbac.authorization.k8s.io/pulp-operator-proxy-role created
rolebinding.rbac.authorization.k8s.io/pulp-operator-leader-election-rolebinding created
rolebinding.rbac.authorization.k8s.io/pulp-operator-manager-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/pulp-operator-manager-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/pulp-operator-proxy-rolebinding created
configmap/pulp-operator-manager-config created
service/pulp-operator-controller-manager-metrics-service created
Error from server (BadRequest): error when creating "STDIN": Deployment in version "v1" cannot be handled as a Deployment: strict decoding error: unknown field "spec.template.spec.containers[1].capabilities"
make: *** [Makefile:225: deploy] Error 1

not sure if i misisng something?
When i do the same on earlier version is works as expected

#2

Hi @rudesome,

“not sure if i misisng something?”

I believe you did it right.
I was taking a look at the error provided and realized that we have an issue in our yaml file:

the above lines should be indented with 2 more spaces (capability is a securityContext configuration).

So, if you are in a rush, you can just edit the manager.yaml file above to be like:

...
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - "ALL"
        livenessProbe:
...

or give me a few minutes to create a PR with this modification.

2 Likes
#3

thank you for the quick response hyagi!

changed the manager yaml file as you suggested and it is deployed successfully now, thanks!

1 Like
#4

nice!!
thank you for letting us know about the error