Closed hrak closed 5 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What steps did you take and what happened:
I tested this provider in a kind test setup, and then everything worked fine. Then i moved it to a 'real' Kubernetes cluster, and the control planes created by CAPN never reach ready state, because all startup/liveness/readiness probes fail.
All startup/liveness/readiness probes are configured/hardcoded to use 127.0.0.1, but since all pods are configured to not use host networking (for obvious reasons), all these checks are hitting the host instead of the pods, and are failing. All services eventually end up in CrashLoopBackoff and the NestedControlPlane never comes up.
I don't know why this does magically work in kind.
Am i missing something, or was the NestedControlPlane never intended to work outside of a kind scenario?
What did you expect to happen:
The NestedControlPlane to come up
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): v1.27.6/etc/os-release
):/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]