apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32104" uid: 6a6056a8-45b0-4237-8420-b382be7a7202 spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T12:24:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.359593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 980.784µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 823.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 912.09µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 1.199681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 1.279129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:54:02Z" - latency: 958.285µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:53:02Z" - latency: 797.151µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:52:02Z" - latency: 951.235µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:51:02Z" - latency: 883.828µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32106" uid: d215a2fd-9737-49d8-90f1-8a90617905b6 spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T12:23:02Z" message: 'load-balancer-api-external: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.120757ms message: 'load-balancer-api-external: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 6.377522ms message: 'load-balancer-api-external: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:59:02Z" - latency: 5.326365ms message: 'load-balancer-api-external: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 6.968436ms message: 'load-balancer-api-external: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:58:02Z" - latency: 5.189474ms message: 'load-balancer-api-external: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 6.782236ms message: 'load-balancer-api-external: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:57:02Z" - latency: 4.677087ms message: 'load-balancer-api-external: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 6.386349ms message: 'load-balancer-api-external: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:56:02Z" - latency: 4.165735ms message: 'load-balancer-api-external: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 6.131096ms message: 'load-balancer-api-external: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:55:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32105" uid: ec11c9a0-a739-4c43-96d0-917790ec015d spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T12:23:02Z" message: 'load-balancer-api-internal: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.081245ms message: 'load-balancer-api-internal: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 6.453924ms message: 'load-balancer-api-internal: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:59:02Z" - latency: 5.340863ms message: 'load-balancer-api-internal: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 7.020238ms message: 'load-balancer-api-internal: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:58:02Z" - latency: 5.454212ms message: 'load-balancer-api-internal: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 6.88116ms message: 'load-balancer-api-internal: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:57:02Z" - latency: 4.697391ms message: 'load-balancer-api-internal: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 6.44312ms message: 'load-balancer-api-internal: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:56:02Z" - latency: 4.786712ms message: 'load-balancer-api-internal: tcp connection to a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 6.205221ms message: 'load-balancer-api-internal: resolved host name a5004649424fe4eb3a5c5d1e5f919a9b-c8fd0e3a26195579.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T12:55:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-network-check-target-ip-10-0-133-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32100" uid: 705394a1-eebd-4eaf-aae3-6d9f1cade7a0 spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T12:24:02Z" message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.338591ms message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 1.40915ms message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 856.476µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 813.517µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 1.071994ms message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 893.613µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:54:02Z" - latency: 822.932µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:53:02Z" - latency: 659.847µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:52:02Z" - latency: 811.735µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:51:02Z" - latency: 876.87µs message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-network-check-target-ip-10-0-142-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32101" uid: 21cebf48-8794-4383-b003-c66f4a0468fd spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T12:24:02Z" message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.259182ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 2.038695ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 1.964523ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 2.11901ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 2.425319ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 1.70175ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:54:02Z" - latency: 1.965712ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:53:02Z" - latency: 2.094745ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:52:02Z" - latency: 2.213194ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:51:02Z" - latency: 2.200083ms message: 'network-check-target-ip-10-0-142-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-network-check-target-ip-10-0-143-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32102" uid: 322bc234-a218-4476-990d-12a7c5cd8bbc spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-25T12:24:02Z" message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299823ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 2.241761ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 1.921764ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 1.939438ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 1.856547ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 1.733447ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:54:02Z" - latency: 2.061155ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:53:02Z" - latency: 2.214422ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:52:02Z" - latency: 1.942701ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:51:02Z" - latency: 2.128066ms message: 'network-check-target-ip-10-0-143-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:50:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T12:17:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-4-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-4.ec2.internal uid: caa5b443-53e9-40d4-b56c-c5c3ff0f819b resourceVersion: "32103" uid: 26ad7f4c-0395-426b-af03-7694aa8f4618 spec: sourcePod: network-check-source-7f44b6dd87-vxntb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T12:23:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 875.792µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:59:02Z" - latency: 1.641192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:59:02Z" - latency: 821.017µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:58:02Z" - latency: 2.185742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:58:02Z" - latency: 834.023µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:57:02Z" - latency: 1.558313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:57:02Z" - latency: 855.603µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:56:02Z" - latency: 1.522245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:56:02Z" - latency: 880.876µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T12:55:02Z" - latency: 1.747085ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T12:55:02Z" kind: List metadata: resourceVersion: ""