apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "50520" uid: 7e39c057-8923-4cac-8c38-4a45b1d6b4a2 spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T19:21:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.220836ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 876.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 948.393µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 1.175633ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 7.512882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:45:42Z" - latency: 1.795421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:42Z" - latency: 2.748925ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:42Z" - latency: 939.468µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:42Z" - latency: 1.401621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:42Z" - latency: 982.98µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "51521" uid: 2def50c1-1fa6-4096-8028-87b8b1e93996 spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:20:42Z" message: 'load-balancer-api-external: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.56344ms message: 'load-balancer-api-external: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:50:42Z" - latency: 6.296583ms message: 'load-balancer-api-external: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:50:42Z" - latency: 3.854417ms message: 'load-balancer-api-external: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 7.595939ms message: 'load-balancer-api-external: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:49:42Z" - latency: 4.915516ms message: 'load-balancer-api-external: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 6.83157ms message: 'load-balancer-api-external: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:48:42Z" - latency: 5.032002ms message: 'load-balancer-api-external: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 7.067397ms message: 'load-balancer-api-external: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:47:42Z" - latency: 5.204878ms message: 'load-balancer-api-external: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 6.697155ms message: 'load-balancer-api-external: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:46:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "51520" uid: 734bb4da-93fa-4a73-8ceb-33531abd4606 spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:20:42Z" message: 'load-balancer-api-internal: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.331117ms message: 'load-balancer-api-internal: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:50:42Z" - latency: 6.379887ms message: 'load-balancer-api-internal: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:50:42Z" - latency: 3.852876ms message: 'load-balancer-api-internal: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 7.615724ms message: 'load-balancer-api-internal: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:49:42Z" - latency: 4.932326ms message: 'load-balancer-api-internal: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 6.701332ms message: 'load-balancer-api-internal: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:48:42Z" - latency: 5.041147ms message: 'load-balancer-api-internal: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 7.038892ms message: 'load-balancer-api-internal: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:47:42Z" - latency: 5.262685ms message: 'load-balancer-api-internal: tcp connection to a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 6.617721ms message: 'load-balancer-api-internal: resolved host name a2c0ef08d0171425c9dfc09bef8d3a35-c6fa0bd98c7be3ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:46:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-network-check-target-ip-10-0-128-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "50517" uid: 61d4d3f1-f2c7-4b8b-a1d1-7a7b9257adfa spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:21:42Z" message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.147798ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 2.00623ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 2.113882ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 2.171137ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 2.572381ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:45:42Z" - latency: 2.134481ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:42Z" - latency: 2.333421ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:42Z" - latency: 3.369554ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:42Z" - latency: 2.09095ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:42Z" - latency: 2.183588ms message: 'network-check-target-ip-10-0-128-188: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-network-check-target-ip-10-0-128-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "50518" uid: e3a87287-febb-4757-8ee1-c2d27ad15695 spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:21:42Z" message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.170688ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 1.127989ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 968.431µs message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 951.518µs message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 7.37391ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:45:42Z" - latency: 883.019µs message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:42Z" - latency: 1.191589ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:42Z" - latency: 1.297253ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:42Z" - latency: 1.16651ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:42Z" - latency: 1.388892ms message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-network-check-target-ip-10-0-134-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "50519" uid: 410b0e4b-d217-4997-bf52-9e2678bf518b spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:21:42Z" message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.01191ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 1.958426ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 1.952821ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 1.964239ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 2.323505ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:45:42Z" - latency: 1.827783ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:42Z" - latency: 1.769373ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:42Z" - latency: 1.945519ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:42Z" - latency: 1.942078ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:42Z" - latency: 1.785631ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:14:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-253-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-253.ec2.internal uid: d14d5f07-936e-4758-b491-f526b4f8bb06 resourceVersion: "51519" uid: 848ca524-e255-4162-9e0b-fe67b47f6ed8 spec: sourcePod: network-check-source-989f8b8dc-btcbl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T19:20:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.117466ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:50:42Z" - latency: 1.787588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:50:42Z" - latency: 951.17µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:49:42Z" - latency: 2.107025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:49:42Z" - latency: 968.53µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:48:42Z" - latency: 1.890097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:48:42Z" - latency: 999.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:47:42Z" - latency: 1.936871ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:47:42Z" - latency: 985.068µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:46:42Z" - latency: 1.885806ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:46:42Z" kind: List metadata: resourceVersion: ""