Robert Hanzlík
Robert Hanzlík
Simply replace the line: `apiVersion: policy/v1beta1` with the following lines: ``` {{- if .Capabilities.APIVersions.Has "policy/v1/PodDisruptionBudget" }} apiVersion: policy/v1 {{- else }} apiVersion: policy/v1beta1 {{- end }} ``` in pdb.yaml
> > maybe we can take the approach of having a seperate AMI with eBPF enabled , similar to how there is a seperate AMI for the GPU support ?...
It is always problem with new release. efs driver team is always pointing to CHANGELOG, but they always forget to update CHANGELOG.
It seems, that here is no reaction, forked, rebuild for go mod and with latest SDK versions. [https://github.com/rubroboletus/skbn](url)
Why The EKS Pod Identity Agent doesn't use the service-account-role-arn for IAM roles for service accounts and you must provide the EKS Pod Identity Agent with permissions in the node...
Main problem is, that on Bottlerocket OS only: ``` ip_vs_sh ip_vs_rr ip_vs_wrr ``` modules are loaded and I cannot find a way, how to load ip_vs_sed / ip_vs_lc modules during...
> Hi, You are right!, I can reproduce the issue and it's because in this code: > > https://github.com/kedacore/keda/blob/2234a6f30df6b9fa83a1b88f1aa609ebee846983/pkg/scalers/cron_scaler.go#L164-L174 > > as the next start is on Monday and next...
> @rubroboletus , there are 2 checks failing: > > * DCO (you need to sign all the commits) > * Static checks (https://github.com/kedacore/keda/actions/runs/10419863822/job/28858769588?pr=6055#step:6:128) > > Could you take a...
> @rubroboletus, can you review this PR #6169 to see it can solve your expectation. In the PR, there is no need for new params. We extract Node stereotypes, node...
/remove-lifecycle stale