apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "47602" uid: 980ab8fe-c9cb-41b4-a2c2-b3e3488b7eec spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-06T19:12:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196218ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 1.232194ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 1.044523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 747.575µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:30:00Z" - latency: 1.143228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:29:00Z" - latency: 836.583µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:28:00Z" - latency: 903.197µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:27:00Z" - latency: 909.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:26:00Z" - latency: 818.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:25:00Z" - latency: 1.282481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "49756" uid: 6d3dc693-f70c-415a-bbf1-ac378fb4ad56 spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T19:11:00Z" message: 'load-balancer-api-external: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.863713ms message: 'load-balancer-api-external: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:35:00Z" - latency: 8.663724ms message: 'load-balancer-api-external: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:35:00Z" - latency: 5.45785ms message: 'load-balancer-api-external: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:34:00Z" - latency: 9.669807ms message: 'load-balancer-api-external: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:34:00Z" - latency: 5.114755ms message: 'load-balancer-api-external: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 8.660398ms message: 'load-balancer-api-external: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:33:00Z" - latency: 5.267805ms message: 'load-balancer-api-external: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 8.583396ms message: 'load-balancer-api-external: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:32:00Z" - latency: 4.4697ms message: 'load-balancer-api-external: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 8.696605ms message: 'load-balancer-api-external: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:31:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "49755" uid: 7d9f10fd-aa1e-423b-8b6d-a4318bf28db9 spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-06T19:11:00Z" message: 'load-balancer-api-internal: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.927278ms message: 'load-balancer-api-internal: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:35:00Z" - latency: 8.576895ms message: 'load-balancer-api-internal: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:35:00Z" - latency: 5.171131ms message: 'load-balancer-api-internal: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:34:00Z" - latency: 9.65192ms message: 'load-balancer-api-internal: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:34:00Z" - latency: 4.267973ms message: 'load-balancer-api-internal: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 8.610163ms message: 'load-balancer-api-internal: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:33:00Z" - latency: 5.237443ms message: 'load-balancer-api-internal: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 8.60597ms message: 'load-balancer-api-internal: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:32:00Z" - latency: 4.475269ms message: 'load-balancer-api-internal: tcp connection to a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 8.61346ms message: 'load-balancer-api-internal: resolved host name a1b533a198f3644f4a54e8f501eb665b-0034de88546fb5d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-06T19:31:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-ip-10-0-128-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "47600" uid: 246b40f6-34d9-40b7-bd8b-d92d91e396f7 spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-06T19:12:00Z" message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.009559ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 2.25952ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 2.386376ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 1.779379ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:30:00Z" - latency: 2.334783ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:29:00Z" - latency: 2.197767ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:28:00Z" - latency: 2.153421ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:27:00Z" - latency: 2.246134ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:26:00Z" - latency: 2.59214ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:25:00Z" - latency: 2.737347ms message: 'network-check-target-ip-10-0-128-126: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-ip-10-0-130-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "47599" uid: 84673752-b646-4423-ade8-22e7d407ae4b spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-06T19:12:00Z" message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.766µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 902.393µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 1.290664ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 786.737µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:30:00Z" - latency: 1.014963ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:29:00Z" - latency: 1.067356ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:28:00Z" - latency: 929.546µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:27:00Z" - latency: 1.056699ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:26:00Z" - latency: 846.898µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:25:00Z" - latency: 922.058µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-ip-10-0-142-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "47601" uid: ebdf295a-8d09-4b66-9892-e3116d7865a7 spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-06T19:12:00Z" message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.945413ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 1.937584ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 2.544176ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 1.912709ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:30:00Z" - latency: 2.638905ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:29:00Z" - latency: 2.456876ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:28:00Z" - latency: 2.579291ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:27:00Z" - latency: 2.235813ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:26:00Z" - latency: 2.282679ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:25:00Z" - latency: 2.651187ms message: 'network-check-target-ip-10-0-142-247: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:24:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-06T19:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: 8e563616-4111-411f-b4ce-25ad88d92ebf resourceVersion: "49754" uid: fe86eb2e-139e-45d4-9d29-b4bc5ff43e60 spec: sourcePod: network-check-source-dbd9cf844-4t2gk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-06T19:11:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 874.544µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:35:00Z" - latency: 1.865982ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T19:35:00Z" - latency: 1.177237ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:34:00Z" - latency: 1.996778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T19:34:00Z" - latency: 1.074603ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:33:00Z" - latency: 1.936589ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T19:33:00Z" - latency: 741.962µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:32:00Z" - latency: 1.842293ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T19:32:00Z" - latency: 1.033752ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-06T19:31:00Z" - latency: 1.86363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-06T19:31:00Z" kind: List metadata: resourceVersion: ""