apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33187" uid: 1e3a3d58-5901-4302-bec4-83bce5bd90e2 spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T17:29:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.239069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 1.503876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 1.317834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 1.272159ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 1.047303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 1.804495ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:59:07Z" - latency: 1.261579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:58:07Z" - latency: 1.260266ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:57:07Z" - latency: 1.449595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:56:07Z" - latency: 1.187775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33189" uid: eb7d6ff6-fdb6-4c11-a0f4-85ce50535562 spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:28:07Z" message: 'load-balancer-api-external: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.782531ms message: 'load-balancer-api-external: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 11.628331ms message: 'load-balancer-api-external: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:04:07Z" - latency: 5.10892ms message: 'load-balancer-api-external: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 7.606206ms message: 'load-balancer-api-external: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:03:07Z" - latency: 4.92876ms message: 'load-balancer-api-external: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 7.954253ms message: 'load-balancer-api-external: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:02:07Z" - latency: 5.097835ms message: 'load-balancer-api-external: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 7.666999ms message: 'load-balancer-api-external: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:01:07Z" - latency: 6.014321ms message: 'load-balancer-api-external: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 11.868583ms message: 'load-balancer-api-external: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:00:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33188" uid: efc1d2a4-3d74-40f3-8d70-fc28b0948099 spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:28:07Z" message: 'load-balancer-api-internal: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.814988ms message: 'load-balancer-api-internal: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 11.638523ms message: 'load-balancer-api-internal: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:04:07Z" - latency: 5.641776ms message: 'load-balancer-api-internal: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 7.431503ms message: 'load-balancer-api-internal: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:03:07Z" - latency: 4.937746ms message: 'load-balancer-api-internal: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 7.964945ms message: 'load-balancer-api-internal: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:02:07Z" - latency: 5.087186ms message: 'load-balancer-api-internal: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 7.583203ms message: 'load-balancer-api-internal: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:01:07Z" - latency: 6.02392ms message: 'load-balancer-api-internal: tcp connection to a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 11.750709ms message: 'load-balancer-api-internal: resolved host name a81162edd84344dbd876f50c2fd677f9-ca6c9ef53e21a839.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T18:00:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-network-check-target-ip-10-0-129-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33185" uid: f7a16105-370e-4f70-a16e-a516f01d7995 spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:29:07Z" message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.076146ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 1.907205ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 2.339462ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 2.142314ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 1.902969ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 2.223978ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:59:07Z" - latency: 2.067267ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:58:07Z" - latency: 2.58412ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:57:07Z" - latency: 2.23321ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:56:07Z" - latency: 3.054478ms message: 'network-check-target-ip-10-0-129-36: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-network-check-target-ip-10-0-139-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33183" uid: 784af100-ff33-4114-8e81-f31678e16fbd spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:29:07Z" message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.016083ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 1.591918ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 874.54µs message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 1.733351ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 979.551µs message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 2.197828ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:59:07Z" - latency: 1.678441ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:58:07Z" - latency: 1.128961ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:57:07Z" - latency: 1.139263ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:56:07Z" - latency: 985.606µs message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-network-check-target-ip-10-0-141-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33184" uid: 2eb37104-b99c-4fa2-8c3a-57fb1e1dd6af spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:29:07Z" message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.698344ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 2.243529ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 2.498922ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 2.452407ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 2.172248ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 2.518406ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:59:07Z" - latency: 2.669698ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:58:07Z" - latency: 2.800535ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:57:07Z" - latency: 2.374669ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:56:07Z" - latency: 3.331151ms message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:22:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-93-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-93.ec2.internal uid: e9bd30ab-8524-46e5-84a4-29290b179f23 resourceVersion: "33186" uid: 918ba1f4-f5a8-48c0-9687-b36a7018ef0a spec: sourcePod: network-check-source-56499946bc-4md7h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T17:28:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.449957ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:04:07Z" - latency: 2.755998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:04:07Z" - latency: 967.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:03:07Z" - latency: 2.298074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:03:07Z" - latency: 1.004401ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:02:07Z" - latency: 2.411316ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:02:07Z" - latency: 1.361897ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:01:07Z" - latency: 1.905289ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:01:07Z" - latency: 1.353822ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T18:00:07Z" - latency: 2.514911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T18:00:07Z" kind: List metadata: resourceVersion: ""