apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "76945" uid: f9eb9828-865b-4cc3-b398-fd98bd5ee80b spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T03:55:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.743µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 973.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:43:03Z" - latency: 900.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:42:03Z" - latency: 1.040797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:41:03Z" - latency: 1.282552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:40:03Z" - latency: 1.078998ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:39:03Z" - latency: 888.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:38:03Z" - latency: 864.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:37:03Z" - latency: 1.037483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:36:03Z" - latency: 1.451554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:35:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "81167" uid: 9d4f440d-b282-4bb6-8046-229afad3f74a spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T03:54:03Z" message: 'load-balancer-api-external: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.421036ms message: 'load-balancer-api-external: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:48:03Z" - latency: 6.800133ms message: 'load-balancer-api-external: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:48:03Z" - latency: 4.632755ms message: 'load-balancer-api-external: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:47:03Z" - latency: 6.792034ms message: 'load-balancer-api-external: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:47:03Z" - latency: 4.608438ms message: 'load-balancer-api-external: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:46:03Z" - latency: 7.060569ms message: 'load-balancer-api-external: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:46:03Z" - latency: 5.363259ms message: 'load-balancer-api-external: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:45:03Z" - latency: 8.571344ms message: 'load-balancer-api-external: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:45:03Z" - latency: 4.377487ms message: 'load-balancer-api-external: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 6.560736ms message: 'load-balancer-api-external: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:44:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "81166" uid: 39582607-fc31-4cd1-9ab9-f5a6ad41ca11 spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T03:54:03Z" message: 'load-balancer-api-internal: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.404399ms message: 'load-balancer-api-internal: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:48:03Z" - latency: 6.885113ms message: 'load-balancer-api-internal: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:48:03Z" - latency: 3.345861ms message: 'load-balancer-api-internal: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:47:03Z" - latency: 6.810571ms message: 'load-balancer-api-internal: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:47:03Z" - latency: 3.64244ms message: 'load-balancer-api-internal: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:46:03Z" - latency: 7.089588ms message: 'load-balancer-api-internal: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:46:03Z" - latency: 5.365994ms message: 'load-balancer-api-internal: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:45:03Z" - latency: 8.605481ms message: 'load-balancer-api-internal: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:45:03Z" - latency: 4.115925ms message: 'load-balancer-api-internal: tcp connection to a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 6.460419ms message: 'load-balancer-api-internal: resolved host name a6f350c63187848959ee8af30bb0ff2b-d10a78004aef2da4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T04:44:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-network-check-target-ip-10-0-134-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "76943" uid: 63c4629f-2375-45c2-a5ac-828cc5f9881d spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T03:55:03Z" message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.556385ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 2.166341ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:43:03Z" - latency: 2.441872ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:42:03Z" - latency: 2.658622ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:41:03Z" - latency: 2.388337ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:40:03Z" - latency: 2.624326ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:39:03Z" - latency: 2.461511ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:38:03Z" - latency: 2.649538ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:37:03Z" - latency: 2.48956ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:36:03Z" - latency: 2.784844ms message: 'network-check-target-ip-10-0-134-114: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:35:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-network-check-target-ip-10-0-136-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "76944" uid: 242c8e8d-9e9f-40f3-9d67-18eaf10f1507 spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T03:55:03Z" message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.35403ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 2.031094ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:43:03Z" - latency: 2.341399ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:42:03Z" - latency: 2.169393ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:41:03Z" - latency: 2.67716ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:40:03Z" - latency: 2.414292ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:39:03Z" - latency: 2.314126ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:38:03Z" - latency: 2.129152ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:37:03Z" - latency: 2.064072ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:36:03Z" - latency: 2.200511ms message: 'network-check-target-ip-10-0-136-104: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:35:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-network-check-target-ip-10-0-138-44 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "76942" uid: 7e067969-2ed9-4405-8ea5-f46ac276ab72 spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T03:55:03Z" message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.527435ms message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 932.976µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:43:03Z" - latency: 919.726µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:42:03Z" - latency: 950.177µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:41:03Z" - latency: 929.813µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:40:03Z" - latency: 1.700837ms message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:39:03Z" - latency: 928.57µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:38:03Z" - latency: 836.746µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:37:03Z" - latency: 985.555µs message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:36:03Z" - latency: 1.061232ms message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:35:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T03:48:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-44-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-44.ec2.internal uid: c1925c9d-38d3-4f2b-9a39-1b321916d960 resourceVersion: "81165" uid: 857caf2f-7279-41f0-af09-675dd3a76dad spec: sourcePod: network-check-source-7d88cb55d8-vdg7f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T03:54:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.05µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:48:03Z" - latency: 1.875271ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T04:48:03Z" - latency: 1.0979ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:47:03Z" - latency: 1.800158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T04:47:03Z" - latency: 1.247241ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:46:03Z" - latency: 2.185459ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T04:46:03Z" - latency: 1.511131ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:45:03Z" - latency: 2.623593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T04:45:03Z" - latency: 891.666µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T04:44:03Z" - latency: 1.63019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T04:44:03Z" kind: List metadata: resourceVersion: ""