apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54015" uid: 020de534-9bdd-4fd4-8094-a52c14edc06d spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T15:28:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.95µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 1.044494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 1.168252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 944.952µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 1.104538ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:52:35Z" - latency: 1.063101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:51:35Z" - latency: 1.051424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:50:35Z" - latency: 1.08273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:49:35Z" - latency: 1.230859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:48:35Z" - latency: 920.645µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54960" uid: 134748b0-c198-4749-8421-386306e178e5 spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T15:27:35Z" message: 'load-balancer-api-external: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.748999ms message: 'load-balancer-api-external: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:57:35Z" - latency: 7.632299ms message: 'load-balancer-api-external: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:57:35Z" - latency: 5.356238ms message: 'load-balancer-api-external: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 7.397345ms message: 'load-balancer-api-external: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:56:35Z" - latency: 3.4613ms message: 'load-balancer-api-external: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 6.674938ms message: 'load-balancer-api-external: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:55:35Z" - latency: 11.462348ms message: 'load-balancer-api-external: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 8.251714ms message: 'load-balancer-api-external: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:54:35Z" - latency: 4.47525ms message: 'load-balancer-api-external: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 6.517411ms message: 'load-balancer-api-external: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:53:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54959" uid: f3561b22-b07a-444f-bcfc-d4e3f7d3ade4 spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T15:27:35Z" message: 'load-balancer-api-internal: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.708735ms message: 'load-balancer-api-internal: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:57:35Z" - latency: 7.604456ms message: 'load-balancer-api-internal: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:57:35Z" - latency: 5.393047ms message: 'load-balancer-api-internal: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 7.361122ms message: 'load-balancer-api-internal: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:56:35Z" - latency: 3.436194ms message: 'load-balancer-api-internal: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 6.64443ms message: 'load-balancer-api-internal: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:55:35Z" - latency: 11.180968ms message: 'load-balancer-api-internal: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 8.235476ms message: 'load-balancer-api-internal: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:54:35Z" - latency: 5.344237ms message: 'load-balancer-api-internal: tcp connection to a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 6.494764ms message: 'load-balancer-api-internal: resolved host name a1726f74684e14eb892bb0f401116777-7ae0b4b8ed5baa14.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T15:53:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-network-check-target-ip-10-0-129-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54013" uid: a6dcfcb4-c4fa-44e2-a314-0a0a1a201aea spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T15:28:35Z" message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286157ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 2.262357ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 3.32503ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 2.114976ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 2.29583ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:52:35Z" - latency: 2.440687ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:51:35Z" - latency: 2.285306ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:50:35Z" - latency: 2.490611ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:49:35Z" - latency: 2.289914ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:48:35Z" - latency: 2.295447ms message: 'network-check-target-ip-10-0-129-138: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-network-check-target-ip-10-0-130-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54011" uid: 7cdf8ff1-da0e-40c6-ba5c-4bea78af972c spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T15:28:35Z" message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099317ms message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 1.369243ms message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 1.092544ms message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 868.659µs message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 952.216µs message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:52:35Z" - latency: 1.578176ms message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:51:35Z" - latency: 1.134815ms message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:50:35Z" - latency: 1.279452ms message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:49:35Z" - latency: 861.59µs message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:48:35Z" - latency: 906.033µs message: 'network-check-target-ip-10-0-130-108: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-network-check-target-ip-10-0-135-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54014" uid: dd72402b-2093-432b-9451-33663de8f28d spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T15:28:35Z" message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.410898ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 2.062248ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 3.23255ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 2.375852ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 2.205404ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:52:35Z" - latency: 2.370908ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:51:35Z" - latency: 2.397902ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:50:35Z" - latency: 2.409302ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:49:35Z" - latency: 1.993672ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:48:35Z" - latency: 2.417773ms message: 'network-check-target-ip-10-0-135-27: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:47:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T15:21:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-108.ec2.internal uid: e5eccf20-71d4-4310-9df6-836ecadb3b08 resourceVersion: "54958" uid: cf1a8411-75dc-421e-b8ae-88bfb1737af7 spec: sourcePod: network-check-source-989f8b8dc-l2s4b targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T15:27:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 793.025µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:57:35Z" - latency: 2.553217ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T15:57:35Z" - latency: 860.208µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:56:35Z" - latency: 2.023105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T15:56:35Z" - latency: 1.090763ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:55:35Z" - latency: 1.711139ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T15:55:35Z" - latency: 1.440375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:54:35Z" - latency: 1.715831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T15:54:35Z" - latency: 830.823µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T15:53:35Z" - latency: 1.751412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T15:53:35Z" kind: List metadata: resourceVersion: ""