Hide Forgot
This is a tracking bug in 4.8 to complete https://issues.redhat.com/browse/OCPPLAN-6006 and specifically https://issues.redhat.com/browse/NE-563.
Thank you Andrew, it works after adding `platform.aws.experimentalPropagateUserTags: true` in install-config.yaml. Since latest nightly builds are all rejected so I verified this with ci build. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.ci-2021-04-27-000602 True False 52m Cluster version is 4.8.0-0.ci-2021-04-27-000602 $ oc get infrastructures.config.openshift.io cluster -oyaml <---snip---> status: platformStatus: aws: region: us-east-1 resourceTags: - key: contact value: hongli - key: customTag value: haha type: AWS $ oc -n openshift-ingress get svc/router-default -oyaml | grep tags service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: contact=hongli,customTag=haha $ oc -n openshift-ingress get svc/router-nlb -oyaml | grep tags service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags: contact=hongli,customTag=haha Goto the AWS console and can see the tags in both Classic and Network Load Balancers.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438