redhat-cop / redhat-cop/gitops-catalog
openshift-devspaces sync fails with included networkpolicies
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 383
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
Using the aggregate/overlays/default overlay
Syncing the checluster returns:
Internal error occurred: failed calling webhook "mchecluster.kb.io": failed to call webhook: Post "https://devspaces-operator-service.openshift-devspaces.svc:443/mutate-org-eclipse-che-v2-checluster?timeout=10s": context deadline exceeded
I was able to work around this by adding this networkpolicy:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-webhook-from-apiserver
spec:
ingress:
- ports:
- protocol: TCP
port: 9443
podSelector: {}
policyTypes:
- Ingress
This appears to be necessary because the kube-apiserver uses host networking, but that should be verified.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the aggregate/overlays/default overlay and reproduce the CheCluster sync failure shown in the report. Investigate whether the included NetworkPolicies allow the kube-apiserver to reach the webhook on port 9443; done means syncing succeeds without the manual allow-webhook-from-apiserver policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100