apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "65263" uid: 43e311ab-9a9e-4f55-a754-02db473ed01c spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T17:07:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.441214ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:49:52Z" - latency: 1.241004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 1.138193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 1.13677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 877.552µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 969.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 810.823µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:43:52Z" - latency: 1.269519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:42:52Z" - latency: 1.215342ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:41:52Z" - latency: 1.714143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:40:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "64317" uid: 9dda312e-1e5b-4904-96f4-e24e9238b6e8 spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:06:52Z" message: 'load-balancer-api-external: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.443245ms message: 'load-balancer-api-external: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 6.519257ms message: 'load-balancer-api-external: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:48:52Z" - latency: 5.233959ms message: 'load-balancer-api-external: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 6.316182ms message: 'load-balancer-api-external: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:47:52Z" - latency: 4.86639ms message: 'load-balancer-api-external: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 7.35656ms message: 'load-balancer-api-external: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:46:52Z" - latency: 4.238794ms message: 'load-balancer-api-external: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 7.049884ms message: 'load-balancer-api-external: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:45:52Z" - latency: 4.765812ms message: 'load-balancer-api-external: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 6.930283ms message: 'load-balancer-api-external: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:44:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "64318" uid: e8a073af-0b79-4b9d-9565-fbb877e33d94 spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T17:06:52Z" message: 'load-balancer-api-internal: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.428393ms message: 'load-balancer-api-internal: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 6.540551ms message: 'load-balancer-api-internal: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:48:52Z" - latency: 6.072462ms message: 'load-balancer-api-internal: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 6.352948ms message: 'load-balancer-api-internal: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:47:52Z" - latency: 4.907785ms message: 'load-balancer-api-internal: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 7.405027ms message: 'load-balancer-api-internal: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:46:52Z" - latency: 3.71983ms message: 'load-balancer-api-internal: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 7.069472ms message: 'load-balancer-api-internal: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:45:52Z" - latency: 4.805024ms message: 'load-balancer-api-internal: tcp connection to a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 6.848014ms message: 'load-balancer-api-internal: resolved host name a427c6e41b6554e6c8ebb99064506497-63f835c69e9f7f24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T17:44:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-ip-10-0-128-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "65262" uid: fc11a9db-ad16-433b-a6b1-fa1ae55a8fb7 spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:07:52Z" message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.359191ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:49:52Z" - latency: 2.748508ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 2.573665ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 2.317155ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 2.192982ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 2.312552ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 1.818924ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:43:52Z" - latency: 2.119321ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:42:52Z" - latency: 2.183799ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:41:52Z" - latency: 2.048765ms message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:40:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-ip-10-0-129-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "65260" uid: 1060b91e-0268-4aeb-bdba-904e65c043fe spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:07:52Z" message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.048454ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:49:52Z" - latency: 2.144636ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 1.838391ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 2.121665ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 1.710847ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 1.896291ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 2.080285ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:43:52Z" - latency: 2.243295ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:42:52Z" - latency: 1.791571ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:41:52Z" - latency: 1.923342ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:40:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-ip-10-0-135-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "65261" uid: 1f43898c-eec2-4dd4-b11a-7958fd0dbad1 spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T17:07:52Z" message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.379779ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:49:52Z" - latency: 1.717654ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 854.926µs message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 1.304496ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 1.031187ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 1.767163ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 1.022495ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:43:52Z" - latency: 1.351638ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:42:52Z" - latency: 1.262454ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:41:52Z" - latency: 1.239669ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:40:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T17:00:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: 6a76f037-dd86-4766-b5d5-225e2368428f resourceVersion: "64316" uid: 8f440c13-d1c6-413f-aca0-bc576a767bfb spec: sourcePod: network-check-source-7d88cb55d8-rhxq4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T17:06:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.452µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:48:52Z" - latency: 1.751684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:48:52Z" - latency: 1.339423ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:47:52Z" - latency: 1.723833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:47:52Z" - latency: 960.088µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:46:52Z" - latency: 1.64623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:46:52Z" - latency: 984.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:45:52Z" - latency: 1.701384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:45:52Z" - latency: 1.215527ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T17:44:52Z" - latency: 1.943319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T17:44:52Z" kind: List metadata: resourceVersion: ""