apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16963" uid: 0446e617-820c-4d55-9ffc-6fef479e0f76 spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T22:24:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.000679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:31:04Z" - latency: 985.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:30:04Z" - latency: 869.661µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 1.031876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 867.092µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 904.791µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 858.716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 968.557µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:24:04Z" - latency: 886.18µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:23:04Z" - latency: 1.003113ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:22:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16297" uid: 02f7c1be-c4bd-420c-a7de-042d8dc6a9a3 spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T22:23:04Z" message: 'load-balancer-api-external: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.483881ms message: 'load-balancer-api-external: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 10.793973ms message: 'load-balancer-api-external: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:29:04Z" - latency: 5.071631ms message: 'load-balancer-api-external: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 8.910834ms message: 'load-balancer-api-external: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:28:04Z" - latency: 4.793746ms message: 'load-balancer-api-external: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 8.102113ms message: 'load-balancer-api-external: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:27:04Z" - latency: 4.806244ms message: 'load-balancer-api-external: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 8.673333ms message: 'load-balancer-api-external: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:26:04Z" - latency: 4.881398ms message: 'load-balancer-api-external: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 8.481117ms message: 'load-balancer-api-external: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:25:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16296" uid: 28cdb8b9-8f7a-4c08-adfd-51158e8dac15 spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T22:23:04Z" message: 'load-balancer-api-internal: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.480228ms message: 'load-balancer-api-internal: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 10.820293ms message: 'load-balancer-api-internal: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:29:04Z" - latency: 5.054521ms message: 'load-balancer-api-internal: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 8.834352ms message: 'load-balancer-api-internal: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:28:04Z" - latency: 4.793471ms message: 'load-balancer-api-internal: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 8.095881ms message: 'load-balancer-api-internal: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:27:04Z" - latency: 3.729106ms message: 'load-balancer-api-internal: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 8.575556ms message: 'load-balancer-api-internal: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:26:04Z" - latency: 4.887503ms message: 'load-balancer-api-internal: tcp connection to a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 8.557766ms message: 'load-balancer-api-internal: resolved host name a999366df815c43428ce08a369265c93-6e68bf107662885a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T22:25:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-ip-10-0-132-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16960" uid: fbab6f11-370f-4c34-bfb5-4893db7db22e spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T22:24:04Z" message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.123µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:31:04Z" - latency: 1.085835ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:30:04Z" - latency: 811.59µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 868.481µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 1.37307ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 904.804µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 808.986µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 808.906µs message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:24:04Z" - latency: 1.334275ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:23:04Z" - latency: 1.354762ms message: 'network-check-target-ip-10-0-132-183: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:22:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-ip-10-0-133-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16961" uid: a4089aa3-1f93-4b31-b172-93ff5dd95410 spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T22:24:04Z" message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.220903ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:31:04Z" - latency: 2.119948ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:30:04Z" - latency: 2.230816ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 2.318868ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 2.049171ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 1.848875ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 1.890673ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 1.914692ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:24:04Z" - latency: 2.321443ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:23:04Z" - latency: 2.240094ms message: 'network-check-target-ip-10-0-133-162: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:22:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-ip-10-0-141-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16962" uid: 613bcaeb-8ea9-4731-b42a-d4be3a7f81c1 spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T22:24:04Z" message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323706ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:31:04Z" - latency: 2.192236ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:30:04Z" - latency: 2.005675ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 1.953362ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 2.074357ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 2.277271ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 2.153773ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 2.249332ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:24:04Z" - latency: 2.400761ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:23:04Z" - latency: 2.298921ms message: 'network-check-target-ip-10-0-141-214: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:22:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T22:17:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-183-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-183.ec2.internal uid: 4541a04b-0da7-4e6f-94c7-652ddd1ac73e resourceVersion: "16295" uid: eb137ee5-fb78-4e81-a5f9-e3d487bbecd0 spec: sourcePod: network-check-source-989f8b8dc-k58w4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T22:23:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 954.187µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:29:04Z" - latency: 1.818337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:29:04Z" - latency: 915.352µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:28:04Z" - latency: 2.221594ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:28:04Z" - latency: 1.039447ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:27:04Z" - latency: 1.671823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:27:04Z" - latency: 894.492µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:26:04Z" - latency: 1.895196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:26:04Z" - latency: 870.491µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T22:25:04Z" - latency: 2.002078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T22:25:04Z" kind: List metadata: resourceVersion: ""