CIS Version : 2.16.1
Build: f5networks/k8s-bigip-ctlr:2.16.1 And earlier
BIGIP Version: ALL
AS3 Version: 3.x
Agent Mode: AS3
Orchestration: K8S
Orchestration Version: k3s v1.28.6+k3s2
Pool Mode: Cluster
Additional Setup details:
Helm 3.14.3
Chart f5-bigip-ctlr-0.0.29
internal Case 00582003
Description
With Ingress mode, the chart can specify an ingressClass name other than the default of "f5"
Installation of the chart will create the specified ingressClass, however the container is not given the required Arg "ingress-class" to be active for that ingressClass.
Thus the implementation does not process any ingress resources.
Steps To Reproduce
1) helm install cis1 f5-stable/f5-bigip-ctlr -f values-cis1.yaml
2) values-ci1.yaml has
Setup Details
CIS Version : 2.16.1 Build: f5networks/k8s-bigip-ctlr:2.16.1 And earlier BIGIP Version: ALL AS3 Version: 3.x
Agent Mode: AS3 Orchestration: K8S Orchestration Version: k3s v1.28.6+k3s2 Pool Mode: Cluster Additional Setup details:
Helm 3.14.3 Chart f5-bigip-ctlr-0.0.29
internal Case 00582003
Description
With Ingress mode, the chart can specify an ingressClass name other than the default of "f5" Installation of the chart will create the specified ingressClass, however the container is not given the required Arg "ingress-class" to be active for that ingressClass.
Thus the implementation does not process any ingress resources.
Steps To Reproduce
1) helm install cis1 f5-stable/f5-bigip-ctlr -f values-cis1.yaml 2) values-ci1.yaml has
Expected Result
That the container has the ingress-class argument for the specified ingressClass
Actual Result
ingressClass "cis1" is created BUT if you Describe the pod there is no " ingress-class=cis1" argument to the container.
Diagnostic Information
Observations (if any)
A manual fix is to add the arg manually to the values.yaml.
Might have bee around for a while.