apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "74116" uid: 043a30ed-8f49-4a60-8d1c-1a767ece4057 spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T15:16:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.25091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 1.028634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:04:21Z" - latency: 1.271287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:03:21Z" - latency: 882.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:02:21Z" - latency: 1.098884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:01:21Z" - latency: 951.832µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:00:21Z" - latency: 1.312196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:59:21Z" - latency: 1.724522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:58:21Z" - latency: 1.171082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:57:21Z" - latency: 871.082µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:56:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "78321" uid: 0fce8f95-f656-42b6-bda8-0f0e660ba1d3 spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T15:15:21Z" message: 'load-balancer-api-external: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.735903ms message: 'load-balancer-api-external: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:09:21Z" - latency: 9.549434ms message: 'load-balancer-api-external: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:09:21Z" - latency: 4.508097ms message: 'load-balancer-api-external: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:08:21Z" - latency: 7.632997ms message: 'load-balancer-api-external: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:08:21Z" - latency: 4.4729ms message: 'load-balancer-api-external: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:07:21Z" - latency: 8.183345ms message: 'load-balancer-api-external: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:07:21Z" - latency: 4.082999ms message: 'load-balancer-api-external: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:06:21Z" - latency: 8.098865ms message: 'load-balancer-api-external: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:06:21Z" - latency: 4.344853ms message: 'load-balancer-api-external: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 7.437409ms message: 'load-balancer-api-external: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:05:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "78320" uid: d4437f1f-3a90-47f1-94f1-efa5fc3d755d spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T15:15:21Z" message: 'load-balancer-api-internal: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.735184ms message: 'load-balancer-api-internal: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:09:21Z" - latency: 9.425331ms message: 'load-balancer-api-internal: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:09:21Z" - latency: 3.841561ms message: 'load-balancer-api-internal: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:08:21Z" - latency: 7.594789ms message: 'load-balancer-api-internal: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:08:21Z" - latency: 4.489245ms message: 'load-balancer-api-internal: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:07:21Z" - latency: 8.147699ms message: 'load-balancer-api-internal: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:07:21Z" - latency: 5.606714ms message: 'load-balancer-api-internal: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:06:21Z" - latency: 8.130578ms message: 'load-balancer-api-internal: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:06:21Z" - latency: 4.561887ms message: 'load-balancer-api-internal: tcp connection to a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 7.483362ms message: 'load-balancer-api-internal: resolved host name a302355a656914d9da6a2e1a107b2d06-f444143871bcd3fe.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T16:05:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-network-check-target-ip-10-0-132-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "74113" uid: 8f91d5e5-9904-492a-b070-1631ffea5377 spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T15:16:21Z" message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088843ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 1.024619ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:04:21Z" - latency: 1.013109ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:03:21Z" - latency: 828.355µs message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:02:21Z" - latency: 920.188µs message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:01:21Z" - latency: 1.398127ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:00:21Z" - latency: 1.630567ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:59:21Z" - latency: 790.893µs message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:58:21Z" - latency: 1.247553ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:57:21Z" - latency: 831.046µs message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:56:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-network-check-target-ip-10-0-136-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "74115" uid: 220e4555-e8f8-41a9-852b-ad9f14553482 spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T15:16:21Z" message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.967443ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 2.175158ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:04:21Z" - latency: 2.122546ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:03:21Z" - latency: 1.99446ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:02:21Z" - latency: 2.184004ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:01:21Z" - latency: 2.440635ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:00:21Z" - latency: 1.923779ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:59:21Z" - latency: 1.779024ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:58:21Z" - latency: 2.046968ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:57:21Z" - latency: 1.976306ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:56:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-network-check-target-ip-10-0-137-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "74114" uid: 513aeaee-8f63-411c-b622-13af5df67915 spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T15:16:21Z" message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.260682ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 2.288409ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:04:21Z" - latency: 2.311511ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:03:21Z" - latency: 1.994021ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:02:21Z" - latency: 2.203613ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:01:21Z" - latency: 2.184451ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:00:21Z" - latency: 2.322295ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:59:21Z" - latency: 2.302739ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:58:21Z" - latency: 2.194677ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:57:21Z" - latency: 2.255301ms message: 'network-check-target-ip-10-0-137-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T15:56:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T15:09:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-155-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-155.ec2.internal uid: ca764b39-984b-4805-aed5-e7fdef4b72cd resourceVersion: "78319" uid: a27f1576-fc30-4563-823c-9c606533f06f spec: sourcePod: network-check-source-65bdbbff45-vz7vb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T15:15:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 755.741µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:09:21Z" - latency: 2.485032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:09:21Z" - latency: 820.264µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:08:21Z" - latency: 1.544893ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:08:21Z" - latency: 1.098875ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:07:21Z" - latency: 1.642662ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:07:21Z" - latency: 931.738µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:06:21Z" - latency: 2.381985ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:06:21Z" - latency: 1.231367ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T16:05:21Z" - latency: 1.817852ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T16:05:21Z" kind: List metadata: resourceVersion: ""