-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manifest deployer tries to create ingress resource before ingress controller is ready #4104
Comments
The issue is marked as stale since no activity has been recorded in 30 days |
The issue is marked as stale since no activity has been recorded in 30 days |
@enp Is this a standard Or is this some custom CRD based ingress? |
The issue is marked as stale since no activity has been recorded in 30 days |
How do you mount them? Can you provide an example? Note that manifest files below |
Run (with mount) example:
Manifest files in folders per files solves problem, thank you! But what is the reason for this limitation? |
K0s will add a "stack" label to all resources that are created via the manifest folder. This is used for automatic pruning (think: |
File name can be also used for stack name, why no? But idea is clear, thank you! |
k0s started via docker with two manifests mounted to /var/lib/k0s/manifests:
No any ingress resource was deployed after k0s completely up and running, but ingress will appear on manual kubectl apply the same manifest
Looks like manifest deployer tries to create ingress resource before nginx ingress controller is ready - so how create ingress resource only after ingress controller via manifest deployer?
The text was updated successfully, but these errors were encountered: