kubernetes-sigs/cluster-api-provider-nested

CAPN doesn't seem to work outside of a kind scenario

hrak opened this issue · 4 comments

hrak commented

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:

  • cluster-api-provider-nested version: main branch
  • Minikube/KIND version: v0.20.0
  • Kubernetes version: (use kubectl version): v1.27.6
  • OS (e.g. from /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]

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten