apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32696" uid: 7c2466a0-878a-48ce-9cd9-53aa7832ebec spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T14:50:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.245949ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 950.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 1.302727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 996.992µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 1.507001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 860.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:20:31Z" - latency: 1.203524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:19:31Z" - latency: 1.265817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:18:31Z" - latency: 961.744µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:17:31Z" - latency: 991.045µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:16:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32698" uid: 16eb3bc7-4aa1-4ffc-bbbc-4bddb5bb2ce5 spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T14:49:31Z" message: 'load-balancer-api-external: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.253562ms message: 'load-balancer-api-external: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 9.048587ms message: 'load-balancer-api-external: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:25:31Z" - latency: 5.362893ms message: 'load-balancer-api-external: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 6.588035ms message: 'load-balancer-api-external: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:24:31Z" - latency: 5.149194ms message: 'load-balancer-api-external: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 8.72764ms message: 'load-balancer-api-external: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:23:31Z" - latency: 6.901955ms message: 'load-balancer-api-external: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 11.15766ms message: 'load-balancer-api-external: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:22:31Z" - latency: 3.919944ms message: 'load-balancer-api-external: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 7.516155ms message: 'load-balancer-api-external: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:21:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32697" uid: bce0e987-cc13-4642-ba0e-124799f834a4 spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T14:49:31Z" message: 'load-balancer-api-internal: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.135964ms message: 'load-balancer-api-internal: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 9.063859ms message: 'load-balancer-api-internal: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:25:31Z" - latency: 5.432528ms message: 'load-balancer-api-internal: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 6.55939ms message: 'load-balancer-api-internal: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:24:31Z" - latency: 4.646004ms message: 'load-balancer-api-internal: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 8.655798ms message: 'load-balancer-api-internal: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:23:31Z" - latency: 6.912315ms message: 'load-balancer-api-internal: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 11.13207ms message: 'load-balancer-api-internal: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:22:31Z" - latency: 3.580087ms message: 'load-balancer-api-internal: tcp connection to a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 7.540084ms message: 'load-balancer-api-internal: resolved host name a7edb4cff348f4802a3b13b016a0f281-075875afcf52c31e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T15:21:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-ip-10-0-133-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32692" uid: 7edebdae-3b4e-425e-a5bb-058c202336d7 spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T14:50:31Z" message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.449526ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 751.096µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 1.094452ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 1.280642ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 951.661µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 899.603µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:20:31Z" - latency: 989.043µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:19:31Z" - latency: 815.526µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:18:31Z" - latency: 1.321455ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:17:31Z" - latency: 963.087µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:16:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-ip-10-0-137-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32693" uid: da7bdee0-a706-45ca-b606-c18c7bec23db spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T14:50:31Z" message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.890752ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 1.895115ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 1.662978ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 1.813952ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 1.91799ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 1.678067ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:20:31Z" - latency: 1.820476ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:19:31Z" - latency: 1.85909ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:18:31Z" - latency: 1.864918ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:17:31Z" - latency: 1.912576ms message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:16:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-ip-10-0-139-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32695" uid: c1b4b948-b67a-4a2c-8b2a-177d510e9fed spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T14:50:31Z" message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.358498ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 2.336056ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 2.332888ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 2.227591ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 2.313598ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 2.303942ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:20:31Z" - latency: 2.26489ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:19:31Z" - latency: 2.82088ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:18:31Z" - latency: 2.15439ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:17:31Z" - latency: 2.501403ms message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:16:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T14:43:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 48aa1ce3-309a-4433-9a6a-efe22e6f4493 resourceVersion: "32694" uid: 384315d4-0959-4921-90ce-8112ee285f7d spec: sourcePod: network-check-source-56499946bc-zgshx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T14:49:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.21507ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:25:31Z" - latency: 1.785678ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T15:25:31Z" - latency: 948.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:24:31Z" - latency: 1.676089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T15:24:31Z" - latency: 784.606µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:23:31Z" - latency: 1.722911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T15:23:31Z" - latency: 1.06258ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:22:31Z" - latency: 1.635632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T15:22:31Z" - latency: 736.637µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T15:21:31Z" - latency: 2.071769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T15:21:31Z" kind: List metadata: resourceVersion: ""