Closed so0k closed 3 years ago
For reference - if you're using EKS IAM, need to patch fsGroup
(this is not a bug, just help for others)
- op: add
path: /spec/template/spec/securityContext
value:
fsGroup: 1000
I could try and do a PR, but I'm handling it through kustomize for now
for others moving to server side applies, need to add the protocol
to the ports see: https://github.com/kubernetes-sigs/structured-merge-diff/issues/130:
patches:
- target:
kind: Deployment
name: sops-secrets-operator-controller-manager
patch: |-
- op: add
path: /spec/template/spec/containers/0/ports/0/protocol
value: TCP
- target:
kind: Service
name: sops-secrets-operator-controller-manager-metrics-service
patch: |-
- op: add
path: /spec/ports/0/protocol
value: TCP
@so0k , are you using helm chart or plain resources via kustomize ? I'm not supporting plain kustomizations, never did any changes to it since helm is preferred way to install this operator. If helm chart - for the fsGroup
- values contain security Context, need to enable it. I'll patch fsGroup
to become same as runAsUser
- 1000
. I'll address some of the issues, but please feel free to send PRs here for kustomizations. Just need to check if these will be overwritten by regenerating the code.
This service is not part of the helm chart either, as I have not implemented prometheus metrics. Thanks for reporting.
closing this issue, won't do any changes right now, if you still need any changes in kustomization please create another ticket
Seems the manager deploy manifest has wrong entrypoint:
Fix for
0.1.9
: