apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "53011" uid: c7d8ddc4-ed70-4175-9c75-67614d33d1e3 spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T11:44:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.491941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 1.332308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 1.038721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 1.076678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:02:05Z" - latency: 1.454852ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:01:05Z" - latency: 884.693µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:00:05Z" - latency: 979.869µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:59:05Z" - latency: 787.542µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:58:05Z" - latency: 819.743µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:57:05Z" - latency: 1.187826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:56:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "54445" uid: c7b5ebf0-8ebe-4d52-8daf-e1f7637a1eef spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T11:43:05Z" message: 'load-balancer-api-external: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.526707ms message: 'load-balancer-api-external: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:07:05Z" - latency: 7.279206ms message: 'load-balancer-api-external: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:07:05Z" - latency: 4.906926ms message: 'load-balancer-api-external: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:06:05Z" - latency: 6.935033ms message: 'load-balancer-api-external: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:06:05Z" - latency: 5.00095ms message: 'load-balancer-api-external: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 8.197722ms message: 'load-balancer-api-external: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:05:05Z" - latency: 6.647462ms message: 'load-balancer-api-external: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 6.734354ms message: 'load-balancer-api-external: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:04:05Z" - latency: 5.117417ms message: 'load-balancer-api-external: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 7.741363ms message: 'load-balancer-api-external: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:03:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "54444" uid: 5a98f5c2-3034-46df-b1e3-93e70ec603f5 spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T11:43:05Z" message: 'load-balancer-api-internal: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.492871ms message: 'load-balancer-api-internal: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:07:05Z" - latency: 7.239563ms message: 'load-balancer-api-internal: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:07:05Z" - latency: 4.891487ms message: 'load-balancer-api-internal: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:06:05Z" - latency: 6.979323ms message: 'load-balancer-api-internal: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:06:05Z" - latency: 5.280832ms message: 'load-balancer-api-internal: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 8.224724ms message: 'load-balancer-api-internal: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:05:05Z" - latency: 6.277217ms message: 'load-balancer-api-internal: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 6.678629ms message: 'load-balancer-api-internal: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:04:05Z" - latency: 5.137442ms message: 'load-balancer-api-internal: tcp connection to a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 7.790079ms message: 'load-balancer-api-internal: resolved host name a667078b5e7934e1fbbeeed5c2d8e38e-5078cbe749473461.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T12:03:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-network-check-target-ip-10-0-135-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "53008" uid: 7281c0e5-23fc-4979-a8ff-603eb3ba3e14 spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T11:44:05Z" message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.940091ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 2.610323ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 2.648022ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 2.29559ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:02:05Z" - latency: 2.44957ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:01:05Z" - latency: 2.320086ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:00:05Z" - latency: 2.704109ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:59:05Z" - latency: 1.93156ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:58:05Z" - latency: 2.339174ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:57:05Z" - latency: 2.152336ms message: 'network-check-target-ip-10-0-135-16: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:56:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-network-check-target-ip-10-0-135-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "53010" uid: a6bfb177-360c-4cc3-9440-4b83f8e024be spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T11:44:05Z" message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.373401ms message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 1.040076ms message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 904.938µs message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 969.952µs message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:02:05Z" - latency: 1.4106ms message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:01:05Z" - latency: 963.096µs message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:00:05Z" - latency: 1.613312ms message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:59:05Z" - latency: 800.035µs message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:58:05Z" - latency: 862.336µs message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:57:05Z" - latency: 1.373654ms message: 'network-check-target-ip-10-0-135-183: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:56:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-network-check-target-ip-10-0-142-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "53009" uid: be02ba50-abe1-42bf-bcef-738106dd7ed8 spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T11:44:05Z" message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.459863ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 2.417262ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 2.615488ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 2.425719ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:02:05Z" - latency: 2.483855ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:01:05Z" - latency: 2.370604ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:00:05Z" - latency: 2.122116ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:59:05Z" - latency: 2.171596ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:58:05Z" - latency: 2.472593ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:57:05Z" - latency: 2.347158ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T11:56:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T11:37:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-183.ec2.internal uid: d7fc4f8f-22f2-414d-9c60-e49eefdffcc8 resourceVersion: "54443" uid: fe9e05cc-407c-4681-b148-364cc4547801 spec: sourcePod: network-check-source-6f8b768455-mg8gb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T11:43:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.17398ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:07:05Z" - latency: 1.847518ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T12:07:05Z" - latency: 865.8µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:06:05Z" - latency: 1.809808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T12:06:05Z" - latency: 895.486µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:05:05Z" - latency: 2.706629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T12:05:05Z" - latency: 784.355µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:04:05Z" - latency: 1.932597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T12:04:05Z" - latency: 888.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T12:03:05Z" - latency: 1.765123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T12:03:05Z" kind: List metadata: resourceVersion: ""