redhat-cop / redhat-cop/gitops-catalog

openshift-devspaces sync fails with included networkpolicies

Open
#419 0 comments 0 reactions 0 assignees View on GitHub

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.