apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "51410" uid: 7d712104-ba88-4d0b-a0e4-96b10d3b0529 spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T18:46:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.29134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 1.296119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 1.127037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 1.23177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 1.088606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:10:17Z" - latency: 1.242992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:09:17Z" - latency: 1.139274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:08:17Z" - latency: 1.185756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:07:17Z" - latency: 1.257411ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:06:17Z" - latency: 1.55144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "52603" uid: bf64c52b-b095-4a2d-bd19-9d0fc1195c82 spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T18:45:17Z" message: 'load-balancer-api-external: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.238927ms message: 'load-balancer-api-external: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:15:17Z" - latency: 7.183134ms message: 'load-balancer-api-external: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:15:17Z" - latency: 6.451677ms message: 'load-balancer-api-external: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 6.694037ms message: 'load-balancer-api-external: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:14:17Z" - latency: 5.026684ms message: 'load-balancer-api-external: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 6.441767ms message: 'load-balancer-api-external: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:13:17Z" - latency: 4.735229ms message: 'load-balancer-api-external: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 9.241659ms message: 'load-balancer-api-external: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:12:17Z" - latency: 4.042143ms message: 'load-balancer-api-external: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 6.825289ms message: 'load-balancer-api-external: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:11:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "52604" uid: fa6d3dea-c9cf-4659-b04e-beee0652de95 spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T18:45:17Z" message: 'load-balancer-api-internal: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.22719ms message: 'load-balancer-api-internal: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:15:17Z" - latency: 7.217044ms message: 'load-balancer-api-internal: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:15:17Z" - latency: 6.4377ms message: 'load-balancer-api-internal: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 6.764305ms message: 'load-balancer-api-internal: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:14:17Z" - latency: 4.952759ms message: 'load-balancer-api-internal: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 6.585372ms message: 'load-balancer-api-internal: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:13:17Z" - latency: 5.634144ms message: 'load-balancer-api-internal: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 9.329608ms message: 'load-balancer-api-internal: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:12:17Z" - latency: 4.013597ms message: 'load-balancer-api-internal: tcp connection to a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 6.851091ms message: 'load-balancer-api-internal: resolved host name a189c639ae2424c7487f6a9e8248d2eb-6904aaa8bcf668b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:11:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-network-check-target-ip-10-0-138-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "51407" uid: 5b5a0ec9-bb46-4cc6-86bc-9ecc52959627 spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T18:46:17Z" message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.500979ms message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 921.693µs message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 825.876µs message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 930.358µs message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 1.226344ms message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:10:17Z" - latency: 928.123µs message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:09:17Z" - latency: 1.274286ms message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:08:17Z" - latency: 897.89µs message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:07:17Z" - latency: 1.36505ms message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:06:17Z" - latency: 1.774752ms message: 'network-check-target-ip-10-0-138-156: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-network-check-target-ip-10-0-140-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "51408" uid: 8258b24a-f6c8-471a-9dc2-edbb83d000dc spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T18:46:17Z" message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.714507ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 1.938443ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 1.666994ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 1.920343ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 1.923861ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:10:17Z" - latency: 1.977992ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:09:17Z" - latency: 2.290877ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:08:17Z" - latency: 2.060252ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:07:17Z" - latency: 2.154617ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:06:17Z" - latency: 2.581505ms message: 'network-check-target-ip-10-0-140-119: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-network-check-target-ip-10-0-141-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "51409" uid: 8fb167d8-490b-4497-a265-56c27abad749 spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T18:46:17Z" message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.183955ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 2.210692ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 2.327702ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 2.03325ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 2.195673ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:10:17Z" - latency: 2.06883ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:09:17Z" - latency: 2.146366ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:08:17Z" - latency: 2.530513ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:07:17Z" - latency: 2.465749ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:06:17Z" - latency: 2.253938ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:05:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T18:39:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-156-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-156.ec2.internal uid: 4bb49b50-0ad3-4acc-bfca-c945711c73a0 resourceVersion: "52602" uid: cc94e48b-4f82-4b00-8301-d3fe0bdb5abd spec: sourcePod: network-check-source-6947749cfc-lzkjq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T18:45:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.589µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:15:17Z" - latency: 1.633058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:15:17Z" - latency: 1.066998ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:14:17Z" - latency: 1.852636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:14:17Z" - latency: 1.112418ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:13:17Z" - latency: 1.899016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:13:17Z" - latency: 1.010001ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:12:17Z" - latency: 1.690938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:12:17Z" - latency: 927.528µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:11:17Z" - latency: 1.730909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:11:17Z" kind: List metadata: resourceVersion: ""