apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "11078" uid: bc0254bb-4c08-4ce0-b460-94fcc430aff9 spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: 172.31.0.1:443 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "21815" uid: a2ee824e-d67a-4157-97a7-3b6fc301d9c2 spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T17:11:36Z" message: 'load-balancer-api-external: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.576703ms message: 'load-balancer-api-external: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:11:36Z" - latency: 7.256851ms message: 'load-balancer-api-external: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:11:36Z" - latency: 3.880362ms message: 'load-balancer-api-external: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:10:36Z" - latency: 8.129599ms message: 'load-balancer-api-external: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:10:36Z" - latency: 6.485977ms message: 'load-balancer-api-external: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:09:36Z" - latency: 8.03884ms message: 'load-balancer-api-external: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:09:36Z" - latency: 6.453737ms message: 'load-balancer-api-external: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:08:36Z" - latency: 8.651712ms message: 'load-balancer-api-external: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:08:36Z" - latency: 5.434101ms message: 'load-balancer-api-external: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:07:36Z" - latency: 7.382337ms message: 'load-balancer-api-external: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:07:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "21814" uid: 68998072-908d-4048-8e04-39818bda086b spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T17:11:36Z" message: 'load-balancer-api-internal: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.608543ms message: 'load-balancer-api-internal: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:11:36Z" - latency: 7.244185ms message: 'load-balancer-api-internal: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:11:36Z" - latency: 4.526214ms message: 'load-balancer-api-internal: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:10:36Z" - latency: 8.04601ms message: 'load-balancer-api-internal: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:10:36Z" - latency: 6.291102ms message: 'load-balancer-api-internal: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:09:36Z" - latency: 7.977083ms message: 'load-balancer-api-internal: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:09:36Z" - latency: 5.673178ms message: 'load-balancer-api-internal: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:08:36Z" - latency: 8.689678ms message: 'load-balancer-api-internal: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:08:36Z" - latency: 5.484661ms message: 'load-balancer-api-internal: tcp connection to afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:07:36Z" - latency: 7.41784ms message: 'load-balancer-api-internal: resolved host name afe4d3ace45c14f4e89afb2a1052999e-0175ae5904245778.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T17:07:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-network-check-target-ip-10-0-132-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "11077" uid: 5c9e97f5-c866-45e7-b8e2-be3951227542 spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: 10.134.0.3:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-network-check-target-ip-10-0-142-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "11075" uid: bb8f6c41-1652-44a9-a8cf-f50733509235 spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: 10.133.0.3:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-network-check-target-ip-10-0-143-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "11074" uid: 0ae4dd79-b820-44f2-aea7-cc0836362018 spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: 10.132.0.3:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T17:05:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-94-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-94.ec2.internal uid: 8a0c99c6-dd50-4cbe-a028-968755b66c74 resourceVersion: "21813" uid: 36e80f5a-f1a0-4222-967d-d2e225379af8 spec: sourcePod: network-check-source-6f8b768455-jk7m8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T17:11:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.197µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:11:36Z" - latency: 1.952306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T17:11:36Z" - latency: 883.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:10:36Z" - latency: 2.049158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T17:10:36Z" - latency: 942.606µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:09:36Z" - latency: 2.328424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T17:09:36Z" - latency: 987.353µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:08:36Z" - latency: 2.119347ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T17:08:36Z" - latency: 961.979µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T17:07:36Z" - latency: 2.200701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T17:07:36Z" kind: List metadata: resourceVersion: ""