apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "45054" uid: ae6dd0b4-337e-415d-9fa9-347a4fd668cb spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T23:45:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 910.987µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 1.039965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 881.679µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:03:27Z" - latency: 1.002481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:02:27Z" - latency: 1.542266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:01:27Z" - latency: 957.333µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:00:27Z" - latency: 899.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:59:27Z" - latency: 1.116282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:58:27Z" - latency: 747.727µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "47017" uid: fe02bd22-6442-4acb-a197-eb0718f718bf spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T23:44:27Z" message: 'load-balancer-api-external: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.16938ms message: 'load-balancer-api-external: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:08:27Z" - latency: 6.225425ms message: 'load-balancer-api-external: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:08:27Z" - latency: 4.87391ms message: 'load-balancer-api-external: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:07:27Z" - latency: 6.744412ms message: 'load-balancer-api-external: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:07:27Z" - latency: 4.98672ms message: 'load-balancer-api-external: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 7.040779ms message: 'load-balancer-api-external: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:06:27Z" - latency: 3.821447ms message: 'load-balancer-api-external: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 6.563864ms message: 'load-balancer-api-external: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:05:27Z" - latency: 5.275118ms message: 'load-balancer-api-external: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 6.5792ms message: 'load-balancer-api-external: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:04:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "47018" uid: 590854ba-d834-4eb2-b0a0-2e139f26af28 spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T23:44:27Z" message: 'load-balancer-api-internal: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.357894ms message: 'load-balancer-api-internal: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:08:27Z" - latency: 6.202621ms message: 'load-balancer-api-internal: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:08:27Z" - latency: 4.501424ms message: 'load-balancer-api-internal: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:07:27Z" - latency: 6.81257ms message: 'load-balancer-api-internal: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:07:27Z" - latency: 5.050534ms message: 'load-balancer-api-internal: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 6.937294ms message: 'load-balancer-api-internal: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:06:27Z" - latency: 3.831291ms message: 'load-balancer-api-internal: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 6.462662ms message: 'load-balancer-api-internal: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:05:27Z" - latency: 5.25968ms message: 'load-balancer-api-internal: tcp connection to a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 6.461755ms message: 'load-balancer-api-internal: resolved host name a09b82fcefcd14b8da515ad1d829b4a6-eab999fdc27f4fe5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T00:04:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-network-check-target-ip-10-0-129-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "45051" uid: 070afb5d-21fa-45fe-b551-8933e761f438 spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:45:27Z" message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.943µs message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 1.042068ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 1.160507ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 1.314323ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:03:27Z" - latency: 898.258µs message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:02:27Z" - latency: 1.233935ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:01:27Z" - latency: 879.592µs message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:00:27Z" - latency: 1.133716ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:59:27Z" - latency: 865.22µs message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:58:27Z" - latency: 1.071489ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-network-check-target-ip-10-0-130-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "45053" uid: 6ad9fd4c-faf2-4dee-ae95-8f3fa3486570 spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:45:27Z" message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.339849ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 2.160469ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 2.194826ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 2.310641ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:03:27Z" - latency: 2.574884ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:02:27Z" - latency: 2.159673ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:01:27Z" - latency: 2.606983ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:00:27Z" - latency: 2.00085ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:59:27Z" - latency: 2.389741ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:58:27Z" - latency: 2.533523ms message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-network-check-target-ip-10-0-143-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "45052" uid: bab39c6f-b13a-4e41-aa18-ca41327b1397 spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T23:45:27Z" message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.260455ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 2.214221ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 2.442429ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 2.3884ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:03:27Z" - latency: 2.647109ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:02:27Z" - latency: 2.165838ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:01:27Z" - latency: 2.636029ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:00:27Z" - latency: 2.01837ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:59:27Z" - latency: 2.308009ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:58:27Z" - latency: 2.159054ms message: 'network-check-target-ip-10-0-143-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T23:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T23:38:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-57.ec2.internal uid: a06a57cf-ec4c-4801-b281-d6245d25ce2f resourceVersion: "47016" uid: f0decbbb-1f91-48dc-a897-1890fa6e7f4e spec: sourcePod: network-check-source-6947749cfc-vw9nh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T23:44:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:08:27Z" - latency: 1.950434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T00:08:27Z" - latency: 891.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:07:27Z" - latency: 1.720526ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T00:07:27Z" - latency: 1.228173ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:06:27Z" - latency: 2.066381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T00:06:27Z" - latency: 1.106753ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:05:27Z" - latency: 1.654025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T00:05:27Z" - latency: 976.511µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T00:04:27Z" - latency: 1.591738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T00:04:27Z" kind: List metadata: resourceVersion: ""