Fernand Galiana
Fernand Galiana
@phunt Hum... which k8s version are your running? also which api group are u using for your pnp?
@phunt Thank you for reporting back! This is related to the deprecations that happened in 1.16. Network policies api group was changed to extensions/v1beta1 to networking.k8s.io/v1. K9s is using the...
@phunt Thank you Patrick! This is indeed tricky and not well handled in k8s. I'll keep this open so I can noodle on better ways to support these deprecation transitions...
@phunt Going thru the issues backlog... I've missed this and you've correctly hinted on it ie crd.projectcalico.org/networkpolicies vs networking.k8s.io/v1/networkpolicies. So that is the problem here as it should be pulling...
@aleksrosz Thanks for the issue. I think it will vary depending on the pod and it's status. ie is the pod and its containers ready and running? Are there init...
@aleksrosz Given the presence of the init container, that message is correct since you are looking at logs at the pod level, all container logs will be streamed out and...
@Noksa Fixed in v0.26.4!
@PeteE Thank you for this issue! In the mean time, if you don't want to see completed cronjobs you can set successfulJobsHistoryLimit=0 in your cronjob spec. Default is set to...
@gazpwc Thank you for reporting this! The current design tries to sanitize the context configurations to ensure unused contexts are wiped. Thus when you specify a different kubeconfig the sanitization...
@necosta I don't currently have access to an M1 but other folks have reported success. Is this still an issue for you?