-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
-
ACM 2.7.0
-
False
-
None
-
False
-
No
-
-
Description of problem:
ACM 2.7 / Submariner 0.14.1
During deployment of Submariner from the UI, metrix proxy daemon set is not created.
- lastTransitionTime: "2023-01-16T21:17:08Z" message: The metrics proxy daemon set does not exist reason: NoMetricsProxyDaemonSet status: "True" type: SubmarinerAgentDegraded
NAME READY STATUS RESTARTS AGE
submariner-addon-86994ff69f-v7dmb 1/1 Running 0 27m
submariner-gateway-882gp 1/1 Running 0 24m
submariner-globalnet-pkdtk 1/1 Running 0 24m
submariner-lighthouse-agent-b656cb6cb-wlj5p 1/1 Running 0 26m
submariner-lighthouse-coredns-5bb7575f69-jrzqq 1/1 Running 0 26m
submariner-lighthouse-coredns-5bb7575f69-kgf85 1/1 Running 0 26m
submariner-operator-7b597fd5df-nwf2z 1/1 Running 0 27m
submariner-routeagent-42std 1/1 Running 0 26m
submariner-routeagent-gtvtv 1/1 Running 0 26m
submariner-routeagent-p867m 1/1 Running 0 26m
submariner-routeagent-pbfw6 1/1 Running 0 24m
submariner-routeagent-s5vnt 1/1 Running 0 26m
submariner-routeagent-wfkcs 1/1 Running 0 26m
submariner-routeagent-xxnfr 1/1 Running 0 26m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE submariner-gateway 1 1 1 1 1 submariner.io/gateway=true 27m submariner-globalnet 1 1 1 1 1 submariner.io/gateway=true 27m submariner-routeagent 7 7 7 7 7 <none> 27m
Debug logs attached.
Note - During deployment by using cli, metrix proxy daemon set created and pod deployment successfully.