apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "9500" uid: cde050b3-0d14-4d48-96d5-18f452cd4ebe spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: 172.31.0.1:443 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "10879" uid: 43e8b61a-ae69-43fc-8965-5a0795cb51a4 spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T19:00:12Z" message: 'load-balancer-api-external: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.052162ms message: 'load-balancer-api-external: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T19:00:12Z" - latency: 7.93626ms message: 'load-balancer-api-external: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T19:00:12Z" - latency: 55.522815ms message: 'load-balancer-api-external: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:59:12Z" - latency: 10.812141ms message: 'load-balancer-api-external: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:59:12Z" - latency: 54.019285ms message: 'load-balancer-api-external: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:58:12Z" - latency: 7.068435ms message: 'load-balancer-api-external: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:58:12Z" - latency: 54.63555ms message: 'load-balancer-api-external: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:57:12Z" - latency: 8.202402ms message: 'load-balancer-api-external: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:57:12Z" - latency: 53.744081ms message: 'load-balancer-api-external: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:56:12Z" - latency: 7.709227ms message: 'load-balancer-api-external: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:56:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "10878" uid: 350bc867-cd15-4b28-ab0a-d4e8f65fe81b spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T19:00:12Z" message: 'load-balancer-api-internal: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.313335ms message: 'load-balancer-api-internal: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T19:00:12Z" - latency: 8.034114ms message: 'load-balancer-api-internal: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T19:00:12Z" - latency: 55.451997ms message: 'load-balancer-api-internal: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:59:12Z" - latency: 10.91659ms message: 'load-balancer-api-internal: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:59:12Z" - latency: 53.991138ms message: 'load-balancer-api-internal: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:58:12Z" - latency: 7.159136ms message: 'load-balancer-api-internal: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:58:12Z" - latency: 55.240369ms message: 'load-balancer-api-internal: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:57:12Z" - latency: 8.165073ms message: 'load-balancer-api-internal: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:57:12Z" - latency: 53.730153ms message: 'load-balancer-api-internal: tcp connection to a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:56:12Z" - latency: 7.920031ms message: 'load-balancer-api-internal: resolved host name a1202a39f531a4b75a62d989b0e898f0-dc9da90034eed6c9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T18:56:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-138-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "9508" uid: f6f04d33-66a5-4e30-94ba-43ff4e346478 spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: 10.133.0.5:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-141-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "9507" uid: 31140a1a-b1c5-41cd-a6df-7c128faaae81 spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: 10.132.0.3:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-ip-10-0-143-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "9509" uid: c8111855-353c-4a14-a994-c991ece66ba5 spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: 10.134.0.5:8080 - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T18:54:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-124.us-west-1.compute.internal uid: c64fdcca-478c-4e80-a170-6723cb7db31b resourceVersion: "10877" uid: b86a8b7d-e464-4de0-9686-72adb42ce550 spec: sourcePod: network-check-source-6f78d59f99-v9l4x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T19:00:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 763.923µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T19:00:12Z" - latency: 1.963892ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T19:00:12Z" - latency: 902.668µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:59:12Z" - latency: 1.520743ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:59:12Z" - latency: 844.24µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:58:12Z" - latency: 2.145068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:58:12Z" - latency: 873.519µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:57:12Z" - latency: 1.659202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:57:12Z" - latency: 986.966µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T18:56:12Z" - latency: 1.692455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T18:56:12Z" kind: List metadata: resourceVersion: ""