apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "47963" uid: 2fc2ac6b-33ed-4a8f-ac67-d583acb31f0f spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T19:45:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.427µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 925.031µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 812.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 938.047µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:03:29Z" - latency: 791.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:02:29Z" - latency: 1.150817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:01:29Z" - latency: 1.262884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:00:29Z" - latency: 986.828µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:59:29Z" - latency: 1.012858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:29Z" - latency: 1.221983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "50063" uid: f6a68bf3-bd6b-466e-ab79-8a295b6a453b spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T19:44:29Z" message: 'load-balancer-api-external: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.184005ms message: 'load-balancer-api-external: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:08:29Z" - latency: 9.171265ms message: 'load-balancer-api-external: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:08:29Z" - latency: 6.167944ms message: 'load-balancer-api-external: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:07:29Z" - latency: 8.345561ms message: 'load-balancer-api-external: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:07:29Z" - latency: 5.129942ms message: 'load-balancer-api-external: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 8.613918ms message: 'load-balancer-api-external: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:06:29Z" - latency: 4.638043ms message: 'load-balancer-api-external: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 8.36694ms message: 'load-balancer-api-external: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:05:29Z" - latency: 3.843289ms message: 'load-balancer-api-external: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 8.199055ms message: 'load-balancer-api-external: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:04:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "50064" uid: 830ca2e6-f207-456c-b767-5fe4a80af8fe spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T19:44:29Z" message: 'load-balancer-api-internal: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.58626ms message: 'load-balancer-api-internal: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:08:29Z" - latency: 9.218166ms message: 'load-balancer-api-internal: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:08:29Z" - latency: 3.689466ms message: 'load-balancer-api-internal: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:07:29Z" - latency: 8.409941ms message: 'load-balancer-api-internal: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:07:29Z" - latency: 5.057368ms message: 'load-balancer-api-internal: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 8.665971ms message: 'load-balancer-api-internal: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:06:29Z" - latency: 4.664115ms message: 'load-balancer-api-internal: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 8.270217ms message: 'load-balancer-api-internal: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:05:29Z" - latency: 3.76821ms message: 'load-balancer-api-internal: tcp connection to a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 8.139499ms message: 'load-balancer-api-internal: resolved host name a98e551b723704337b1ee0e6aab2b99c-2c5a6925c1f692ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T20:04:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-network-check-target-ip-10-0-128-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "47961" uid: 7b16394b-a4a7-4364-bc9c-9612b86f0a8d spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T19:45:29Z" message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.214931ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 2.671162ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 2.289944ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 2.329496ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:03:29Z" - latency: 1.980451ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:02:29Z" - latency: 2.390387ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:01:29Z" - latency: 2.249989ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:00:29Z" - latency: 2.405957ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:59:29Z" - latency: 2.264131ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:29Z" - latency: 2.279501ms message: 'network-check-target-ip-10-0-128-21: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-network-check-target-ip-10-0-133-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "47960" uid: de832041-1500-41f3-9838-d0c9b0bc0dfc spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T19:45:29Z" message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.388816ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 1.006806ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 1.615272ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 1.089256ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:03:29Z" - latency: 1.015739ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:02:29Z" - latency: 1.002786ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:01:29Z" - latency: 1.165228ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:00:29Z" - latency: 857.367µs message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:59:29Z" - latency: 913.293µs message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:29Z" - latency: 1.448732ms message: 'network-check-target-ip-10-0-133-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-network-check-target-ip-10-0-136-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "47962" uid: a2d13bf2-b020-4fdc-915f-955ae3afe591 spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T19:45:29Z" message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.303359ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 2.299964ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 1.963584ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 2.338831ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:03:29Z" - latency: 2.486283ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:02:29Z" - latency: 2.376267ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:01:29Z" - latency: 2.407168ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:00:29Z" - latency: 2.183203ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:59:29Z" - latency: 2.415975ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:58:29Z" - latency: 1.942969ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T19:57:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T19:38:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-145-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-145.ec2.internal uid: 5bed5cc0-85e0-4847-a337-274661aff422 resourceVersion: "50062" uid: 1b979603-ba77-4883-b071-72437b303f95 spec: sourcePod: network-check-source-dbd9cf844-cl25g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T19:44:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.421µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:08:29Z" - latency: 2.02586ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T20:08:29Z" - latency: 982.779µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:07:29Z" - latency: 1.914562ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T20:07:29Z" - latency: 812.882µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:06:29Z" - latency: 1.981664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T20:06:29Z" - latency: 926.096µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:05:29Z" - latency: 1.810988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T20:05:29Z" - latency: 839.476µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T20:04:29Z" - latency: 2.198726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T20:04:29Z" kind: List metadata: resourceVersion: ""