apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32472" uid: 4a720e0d-4f50-4d1a-a1bb-73009a476d72 spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T22:08:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.969421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 1.063829ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 880.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 903.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 924.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 1.189837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:38:21Z" - latency: 945.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:37:21Z" - latency: 832.32µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:36:21Z" - latency: 1.062703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:35:21Z" - latency: 912.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:34:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32474" uid: 1046f309-9562-422c-a55c-708b1a798326 spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T22:07:21Z" message: 'load-balancer-api-external: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.931642ms message: 'load-balancer-api-external: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 9.184008ms message: 'load-balancer-api-external: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:43:21Z" - latency: 3.780294ms message: 'load-balancer-api-external: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 8.96011ms message: 'load-balancer-api-external: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:42:21Z" - latency: 4.614768ms message: 'load-balancer-api-external: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 21.624599ms message: 'load-balancer-api-external: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:41:21Z" - latency: 4.99339ms message: 'load-balancer-api-external: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 9.815707ms message: 'load-balancer-api-external: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:40:21Z" - latency: 5.196094ms message: 'load-balancer-api-external: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 7.218447ms message: 'load-balancer-api-external: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:39:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32475" uid: 4155c9d1-fedb-4644-8e2a-864cc0f77435 spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T22:07:21Z" message: 'load-balancer-api-internal: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.974691ms message: 'load-balancer-api-internal: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 9.127986ms message: 'load-balancer-api-internal: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:43:21Z" - latency: 4.457237ms message: 'load-balancer-api-internal: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 8.844671ms message: 'load-balancer-api-internal: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:42:21Z" - latency: 4.607695ms message: 'load-balancer-api-internal: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 21.5724ms message: 'load-balancer-api-internal: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:41:21Z" - latency: 4.730838ms message: 'load-balancer-api-internal: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 9.794726ms message: 'load-balancer-api-internal: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:40:21Z" - latency: 5.418284ms message: 'load-balancer-api-internal: tcp connection to ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 7.189087ms message: 'load-balancer-api-internal: resolved host name ac06dad1100c74de2ac854b2657435b4-fb1337410321224e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T22:39:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-network-check-target-ip-10-0-131-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32469" uid: 28c4e363-16ca-4eae-a3e3-54cbade2cb63 spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T22:08:21Z" message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.28244ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 2.32267ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 1.840996ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 2.368745ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 2.687089ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 2.526438ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:38:21Z" - latency: 2.39491ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:37:21Z" - latency: 2.11783ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:36:21Z" - latency: 2.22293ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:35:21Z" - latency: 2.11692ms message: 'network-check-target-ip-10-0-131-183: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:34:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-network-check-target-ip-10-0-131-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32471" uid: 95707462-1c87-4f70-9b56-09850105d0e9 spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T22:08:21Z" message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.842235ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 2.171073ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 2.505341ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 2.357313ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 2.41025ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 2.528226ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:38:21Z" - latency: 2.321294ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:37:21Z" - latency: 2.279154ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:36:21Z" - latency: 2.167175ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:35:21Z" - latency: 2.204013ms message: 'network-check-target-ip-10-0-131-69: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:34:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-network-check-target-ip-10-0-136-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32468" uid: 401c31c8-8cb8-4dc0-89ab-a6e7810f483e spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T22:08:21Z" message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140153ms message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 901.023µs message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 853.864µs message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 949.424µs message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 1.390214ms message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 1.052871ms message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:38:21Z" - latency: 1.245645ms message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:37:21Z" - latency: 1.355676ms message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:36:21Z" - latency: 885.716µs message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:35:21Z" - latency: 845.698µs message: 'network-check-target-ip-10-0-136-66: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:34:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T22:01:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-66-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-66.ec2.internal uid: bd8d84c4-a206-438c-8985-e22059943139 resourceVersion: "32470" uid: 44cf2fd8-00f9-4604-90c3-711707385395 spec: sourcePod: network-check-source-7cbc45fddc-fgp46 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T22:07:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 740.183µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:43:21Z" - latency: 2.247872ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T22:43:21Z" - latency: 1.073161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:42:21Z" - latency: 1.655616ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T22:42:21Z" - latency: 868.624µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:41:21Z" - latency: 1.773025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T22:41:21Z" - latency: 795.767µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:40:21Z" - latency: 2.259815ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T22:40:21Z" - latency: 1.288007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T22:39:21Z" - latency: 1.725951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T22:39:21Z" kind: List metadata: resourceVersion: ""