apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61162" uid: a6884b03-3ad4-4654-997e-86fa823e82aa spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T20:10:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.16633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 1.31356ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 1.25148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 1.093054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 1.203939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 1.448131ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:40:33Z" - latency: 1.279816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:39:33Z" - latency: 1.18899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:38:33Z" - latency: 883.712µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:37:33Z" - latency: 1.249265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:36:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61163" uid: 5a3a3b65-c26f-4898-86b8-653dc2da41c8 spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T20:09:33Z" message: 'load-balancer-api-external: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.715891ms message: 'load-balancer-api-external: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 7.903863ms message: 'load-balancer-api-external: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:45:33Z" - latency: 5.751232ms message: 'load-balancer-api-external: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 10.617101ms message: 'load-balancer-api-external: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:44:33Z" - latency: 3.673918ms message: 'load-balancer-api-external: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 9.900588ms message: 'load-balancer-api-external: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:43:33Z" - latency: 4.863088ms message: 'load-balancer-api-external: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 11.067853ms message: 'load-balancer-api-external: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:42:33Z" - latency: 4.38865ms message: 'load-balancer-api-external: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 11.101626ms message: 'load-balancer-api-external: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:41:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61164" uid: c5f85da1-0ae0-4065-a901-96c9a09edcf6 spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T20:09:33Z" message: 'load-balancer-api-internal: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.745179ms message: 'load-balancer-api-internal: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 7.881288ms message: 'load-balancer-api-internal: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:45:33Z" - latency: 9.464873ms message: 'load-balancer-api-internal: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 10.521919ms message: 'load-balancer-api-internal: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:44:33Z" - latency: 4.383644ms message: 'load-balancer-api-internal: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 9.86699ms message: 'load-balancer-api-internal: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:43:33Z" - latency: 4.845543ms message: 'load-balancer-api-internal: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 11.037081ms message: 'load-balancer-api-internal: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:42:33Z" - latency: 4.151601ms message: 'load-balancer-api-internal: tcp connection to a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 11.049415ms message: 'load-balancer-api-internal: resolved host name a3e6cf8e75992406c897e31c454dfa29-dcc4770ef11d9417.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T20:41:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-ip-10-0-128-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61159" uid: e46e3372-9eb6-4887-a5fc-eb2743c39309 spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T20:10:33Z" message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.089548ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 1.955375ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 2.116444ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 2.379529ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 2.494349ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 2.289886ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:40:33Z" - latency: 1.881036ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:39:33Z" - latency: 2.266973ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:38:33Z" - latency: 2.396477ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:37:33Z" - latency: 2.4685ms message: 'network-check-target-ip-10-0-128-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:36:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-ip-10-0-134-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61158" uid: e9bd8787-29e2-4d31-acb3-382aaf7d912c spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T20:10:33Z" message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.305µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 872.413µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 905.857µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 1.138993ms message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 1.164973ms message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 972.185µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:40:33Z" - latency: 852.484µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:39:33Z" - latency: 1.095552ms message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:38:33Z" - latency: 892.181µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:37:33Z" - latency: 940.939µs message: 'network-check-target-ip-10-0-134-169: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:36:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-ip-10-0-140-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61160" uid: 0ffaec90-b591-46eb-a7cd-ec0ff423565e spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T20:10:33Z" message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.316756ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 2.276962ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 2.551927ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 2.458709ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 2.386689ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 2.080873ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:40:33Z" - latency: 2.320923ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:39:33Z" - latency: 2.586408ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:38:33Z" - latency: 2.556483ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:37:33Z" - latency: 3.122843ms message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:36:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T20:03:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-169.ec2.internal uid: 9f73e7e7-e0f2-42bd-895e-90eb667cdca2 resourceVersion: "61161" uid: 32eb61be-9d04-476a-9291-cea0eaa0ed1b spec: sourcePod: network-check-source-7bc5b6bf85-wb7gg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T20:09:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.041684ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:45:33Z" - latency: 1.813924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T20:45:33Z" - latency: 941.343µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:44:33Z" - latency: 1.773823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T20:44:33Z" - latency: 980.798µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:43:33Z" - latency: 1.678489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T20:43:33Z" - latency: 847.788µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:42:33Z" - latency: 1.776274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T20:42:33Z" - latency: 1.587001ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T20:41:33Z" - latency: 2.001925ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T20:41:33Z" kind: List metadata: resourceVersion: ""