apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "52983" uid: 594fd7ee-6f50-4660-b43b-9f84ea73e449 spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T19:16:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.836µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:47Z" - latency: 979.703µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:47Z" - latency: 1.071074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:47Z" - latency: 851.776µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:47Z" - latency: 970.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:47Z" - latency: 1.641097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 1.072515ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 1.026998ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 1.123623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 1.052578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "48178" uid: ca4df78f-4784-4656-9347-69d969baa602 spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:15:47Z" message: 'load-balancer-api-external: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.05771ms message: 'load-balancer-api-external: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 10.098654ms message: 'load-balancer-api-external: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:39:47Z" - latency: 5.346995ms message: 'load-balancer-api-external: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 8.898153ms message: 'load-balancer-api-external: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:38:47Z" - latency: 4.978482ms message: 'load-balancer-api-external: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 11.844061ms message: 'load-balancer-api-external: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:37:47Z" - latency: 5.780935ms message: 'load-balancer-api-external: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 8.28456ms message: 'load-balancer-api-external: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:36:47Z" - latency: 5.845912ms message: 'load-balancer-api-external: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - latency: 8.56429ms message: 'load-balancer-api-external: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:35:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "48179" uid: 7a9edc45-8e1e-4a2c-9b9e-c0d93ba3909b spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T19:15:47Z" message: 'load-balancer-api-internal: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.788984ms message: 'load-balancer-api-internal: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 10.110638ms message: 'load-balancer-api-internal: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:39:47Z" - latency: 5.336648ms message: 'load-balancer-api-internal: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 8.924233ms message: 'load-balancer-api-internal: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:38:47Z" - latency: 4.397947ms message: 'load-balancer-api-internal: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 11.882402ms message: 'load-balancer-api-internal: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:37:47Z" - latency: 5.737952ms message: 'load-balancer-api-internal: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 8.345743ms message: 'load-balancer-api-internal: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:36:47Z" - latency: 5.637413ms message: 'load-balancer-api-internal: tcp connection to a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - latency: 8.46547ms message: 'load-balancer-api-internal: resolved host name a5482ec3657b04e7bbc43d4af91e8fbc-02c2afd0f6478209.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:35:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-network-check-target-ip-10-0-128-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "52982" uid: 45498441-3f72-4e15-adac-2c56059b1cd3 spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:16:47Z" message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.859495ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:47Z" - latency: 2.163315ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:47Z" - latency: 2.322162ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:47Z" - latency: 2.430598ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:47Z" - latency: 2.188822ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:47Z" - latency: 2.137595ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 1.917789ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 2.382648ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 2.126696ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 2.114819ms message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-network-check-target-ip-10-0-130-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "52981" uid: 156b0e04-66c5-4993-95d2-dce07bb14ef8 spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:16:47Z" message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.008186ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:47Z" - latency: 2.126001ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:47Z" - latency: 2.200919ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:47Z" - latency: 2.260922ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:47Z" - latency: 2.309422ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:47Z" - latency: 2.031923ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 1.979213ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 2.345089ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 2.335535ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 2.397645ms message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-network-check-target-ip-10-0-138-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "52980" uid: 1ca11317-92ac-4afa-9863-396f346d897c spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T19:16:47Z" message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.018316ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:44:47Z" - latency: 1.20317ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:43:47Z" - latency: 869.436µs message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:42:47Z" - latency: 1.039145ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:41:47Z" - latency: 870.953µs message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:40:47Z" - latency: 808.631µs message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 842.949µs message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 1.32475ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 1.168818ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 1.187284ms message: 'network-check-target-ip-10-0-138-105: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T19:09:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-105-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-105.ec2.internal uid: aad8eb7e-17fe-4d59-9b0e-9ceb6a74069a resourceVersion: "48177" uid: 276f1d3a-fc9c-46ca-a0ba-24534c8d69a3 spec: sourcePod: network-check-source-989f8b8dc-s2fhk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T19:15:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.933µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:39:47Z" - latency: 2.437118ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:39:47Z" - latency: 942.035µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:38:47Z" - latency: 2.400398ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:38:47Z" - latency: 884.12µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:37:47Z" - latency: 1.67638ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:37:47Z" - latency: 872.964µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:36:47Z" - latency: 1.800503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:36:47Z" - latency: 1.017075ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:35:47Z" - latency: 1.805807ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:35:47Z" kind: List metadata: resourceVersion: ""