apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "53891" uid: 58d5aee5-029f-42aa-a2ff-7b907bcb4b27 spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T11:18:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.312431ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 1.237268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 1.273869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 1.701653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 1.355566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:40Z" - latency: 2.625557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:40Z" - latency: 1.352588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:40Z" - latency: 1.186174ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:40Z" - latency: 1.892981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:40Z" - latency: 1.087716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "54818" uid: c387aec1-67b6-425f-8efb-9a697b580b98 spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T11:17:40Z" message: 'load-balancer-api-external: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.183579ms message: 'load-balancer-api-external: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:47:40Z" - latency: 7.482472ms message: 'load-balancer-api-external: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:47:40Z" - latency: 4.751337ms message: 'load-balancer-api-external: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 7.115817ms message: 'load-balancer-api-external: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:46:40Z" - latency: 5.131118ms message: 'load-balancer-api-external: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 7.305088ms message: 'load-balancer-api-external: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:45:40Z" - latency: 4.569342ms message: 'load-balancer-api-external: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 7.142583ms message: 'load-balancer-api-external: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:44:40Z" - latency: 5.764624ms message: 'load-balancer-api-external: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 7.713233ms message: 'load-balancer-api-external: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:43:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "54819" uid: 93207bca-80d4-4502-a71e-63bb6a0e7a4f spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T11:17:40Z" message: 'load-balancer-api-internal: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.339812ms message: 'load-balancer-api-internal: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:47:40Z" - latency: 7.494659ms message: 'load-balancer-api-internal: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:47:40Z" - latency: 4.024834ms message: 'load-balancer-api-internal: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 7.048444ms message: 'load-balancer-api-internal: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:46:40Z" - latency: 5.120162ms message: 'load-balancer-api-internal: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 7.40732ms message: 'load-balancer-api-internal: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:45:40Z" - latency: 4.57711ms message: 'load-balancer-api-internal: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 7.109234ms message: 'load-balancer-api-internal: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:44:40Z" - latency: 4.763044ms message: 'load-balancer-api-internal: tcp connection to add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 7.780915ms message: 'load-balancer-api-internal: resolved host name add06b539f9404939bd9de6c6f916b32-90dc1431c99af290.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T11:43:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-ip-10-0-130-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "53888" uid: 33748986-e227-4b58-b423-4f3e4d458ad0 spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-16T11:18:40Z" message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.29747ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 2.374663ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 2.121827ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 2.248495ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 2.188591ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:40Z" - latency: 2.579261ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:40Z" - latency: 2.660848ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:40Z" - latency: 2.424762ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:40Z" - latency: 2.433912ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:40Z" - latency: 2.099536ms message: 'network-check-target-ip-10-0-130-16: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-ip-10-0-135-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "53890" uid: 9a8768fb-7870-4cfc-8294-62ae8ce97b59 spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T11:18:40Z" message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.724µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 962.069µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 1.078224ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 937.988µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 1.009846ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:40Z" - latency: 1.299968ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:40Z" - latency: 1.722319ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:40Z" - latency: 1.00672ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:40Z" - latency: 2.269987ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:40Z" - latency: 880.623µs message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-ip-10-0-139-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "53889" uid: c3351551-0e03-43e6-9852-93f3c6310c82 spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T11:18:40Z" message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.989173ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 1.967246ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 1.882004ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 1.979706ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 2.099512ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:42:40Z" - latency: 2.638435ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:41:40Z" - latency: 1.932219ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:40:40Z" - latency: 1.785264ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:39:40Z" - latency: 2.23739ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:38:40Z" - latency: 1.869715ms message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:37:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T11:11:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-184-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-184.ec2.internal uid: 964a8321-adfb-44a1-9a81-04aedacfec38 resourceVersion: "54817" uid: 7d1ddde5-aa0e-4f95-89c5-4683213eecf9 spec: sourcePod: network-check-source-869dcfcdcd-5jghx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T11:17:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 971.2µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:47:40Z" - latency: 1.982515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:47:40Z" - latency: 1.422759ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:46:40Z" - latency: 1.984988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:46:40Z" - latency: 1.061994ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:45:40Z" - latency: 1.893486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:45:40Z" - latency: 1.060339ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:44:40Z" - latency: 2.046209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:44:40Z" - latency: 926.21µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T11:43:40Z" - latency: 2.361004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T11:43:40Z" kind: List metadata: resourceVersion: ""