apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "54069" uid: 16d6f3ec-97b0-4db7-9340-17f8b7c3dd42 spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T14:31:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.983µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 879.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 1.537148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 1.043721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 796.284µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:55:59Z" - latency: 1.15766ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:54:59Z" - latency: 941.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:53:59Z" - latency: 1.015761ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:59Z" - latency: 1.161841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:59Z" - latency: 1.15704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "55256" uid: dcdbd595-567b-4a76-b4bb-9b9e73cc703a spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T14:30:59Z" message: 'load-balancer-api-external: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.572603ms message: 'load-balancer-api-external: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:00:59Z" - latency: 6.973473ms message: 'load-balancer-api-external: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:00:59Z" - latency: 5.30476ms message: 'load-balancer-api-external: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 7.716466ms message: 'load-balancer-api-external: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:59:59Z" - latency: 5.039808ms message: 'load-balancer-api-external: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 6.674911ms message: 'load-balancer-api-external: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:58:59Z" - latency: 4.695832ms message: 'load-balancer-api-external: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 7.810919ms message: 'load-balancer-api-external: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:57:59Z" - latency: 3.476692ms message: 'load-balancer-api-external: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 9.215172ms message: 'load-balancer-api-external: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "55257" uid: b1ecf105-ca7f-49c1-8102-05508447fe27 spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T14:30:59Z" message: 'load-balancer-api-internal: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.46125ms message: 'load-balancer-api-internal: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:00:59Z" - latency: 6.913526ms message: 'load-balancer-api-internal: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T15:00:59Z" - latency: 4.423459ms message: 'load-balancer-api-internal: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 7.664666ms message: 'load-balancer-api-internal: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:59:59Z" - latency: 4.98181ms message: 'load-balancer-api-internal: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 6.625866ms message: 'load-balancer-api-internal: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:58:59Z" - latency: 4.717341ms message: 'load-balancer-api-internal: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 7.71956ms message: 'load-balancer-api-internal: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:57:59Z" - latency: 7.798735ms message: 'load-balancer-api-internal: tcp connection to a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 9.191869ms message: 'load-balancer-api-internal: resolved host name a455fb8b33d5648f780c1be6194001a2-bfdedc9bd4e2a6ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T14:56:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-network-check-target-ip-10-0-133-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "54068" uid: 19dfb8bf-73f3-4a9a-9170-841bb3532453 spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:31:59Z" message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.541163ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 855.12µs message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 1.65317ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 1.016097ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 930.936µs message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:55:59Z" - latency: 998.609µs message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:54:59Z" - latency: 1.036556ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:53:59Z" - latency: 1.691917ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:59Z" - latency: 1.13982ms message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:59Z" - latency: 907.52µs message: 'network-check-target-ip-10-0-133-55: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-network-check-target-ip-10-0-136-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "54066" uid: 551dc065-2ba1-4b97-972d-5697e4ecc4b5 spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:31:59Z" message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.295256ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 2.01077ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 2.440804ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 2.215792ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 2.130978ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:55:59Z" - latency: 2.067286ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:54:59Z" - latency: 2.36262ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:53:59Z" - latency: 2.35268ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:59Z" - latency: 2.333766ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:59Z" - latency: 2.156513ms message: 'network-check-target-ip-10-0-136-93: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-network-check-target-ip-10-0-140-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "54067" uid: 79405f9e-4ff8-4581-8ec6-031744ff5f4d spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T14:31:59Z" message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.890733ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 1.608498ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 2.097055ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 1.965714ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 1.637237ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:55:59Z" - latency: 1.747981ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:54:59Z" - latency: 1.680233ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:53:59Z" - latency: 1.986891ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:52:59Z" - latency: 1.897641ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:51:59Z" - latency: 1.79302ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:50:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T14:24:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-55.ec2.internal uid: bad6935a-ee50-4ea2-93d5-02c9e451cb3f resourceVersion: "55255" uid: 1bc89847-2a2b-4604-841f-74b2e9423972 spec: sourcePod: network-check-source-869dcfcdcd-m5nnq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T14:30:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.933µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T15:00:59Z" - latency: 1.762163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T15:00:59Z" - latency: 1.112517ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:59:59Z" - latency: 1.86264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:59:59Z" - latency: 928.843µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:58:59Z" - latency: 1.647078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:58:59Z" - latency: 1.157601ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:57:59Z" - latency: 1.905165ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:57:59Z" - latency: 1.187366ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T14:56:59Z" - latency: 1.956709ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T14:56:59Z" kind: List metadata: resourceVersion: ""