You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
args:
# NOTE: helm has difficulty with values using `-`; `_` are used for naming# and are replaced with `-` during rendering.# REQUIRED Params# Huttley-V13Abigip_url: https://10.155.85.65bigip_partition: cis1# OPTIONAL PARAMS -- uncomment and provide values for those you wish to use.# verify_interval:# node-poll_interval:# log_level:# python_basedir: ~# VXLAN# openshift_sdn_name:# flannel_name:# KUBERNETES#default_ingress_ip: 10.2.20.166# kubeconfig:# namespaces: ["foo", "bar"]#namespaces: ["ingress"]# namespace_label:# node_label_selector:pool_member_type: cluster# resolve_ingress_names:# running_in_cluster:# use_node_internal:# use_secrets:insecure: truecustom-resource-mode: falselog-as3-response: truelog-level: DEBUG# gtm-bigip-password# gtm-bigip-url# gtm-bigip-username# ipam : trueingress-class: cis1 <<<<<<<<<<<<<<=================
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: