apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "173342" uid: bea0b276-751b-40e9-b2c8-f731e2024a24 spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T12:00:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.166µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 1.456458ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 1.189693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 899.775µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:42:54Z" - latency: 836.746µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:41:54Z" - latency: 904.999µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:40:54Z" - latency: 966.627µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:39:54Z" - latency: 1.373225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:38:54Z" - latency: 921.6µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:37:54Z" - latency: 904.302µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:36:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "174881" uid: 7877f464-d050-4456-8508-5163d40671de spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T11:59:54Z" message: 'load-balancer-api-external: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 62.963739ms message: 'load-balancer-api-external: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:47:54Z" - latency: 40.492461ms message: 'load-balancer-api-external: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:47:54Z" - latency: 52.550788ms message: 'load-balancer-api-external: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:46:54Z" - latency: 7.714625ms message: 'load-balancer-api-external: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:46:54Z" - latency: 54.794877ms message: 'load-balancer-api-external: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 7.701404ms message: 'load-balancer-api-external: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:45:54Z" - latency: 55.229565ms message: 'load-balancer-api-external: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 7.80859ms message: 'load-balancer-api-external: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:44:54Z" - latency: 49.274235ms message: 'load-balancer-api-external: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 7.087899ms message: 'load-balancer-api-external: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:43:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "174882" uid: 250b49c5-1d89-4122-9e12-24ce5fd8b62e spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T11:59:54Z" message: 'load-balancer-api-internal: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 63.346091ms message: 'load-balancer-api-internal: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:47:54Z" - latency: 42.111906ms message: 'load-balancer-api-internal: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:47:54Z" - latency: 55.6907ms message: 'load-balancer-api-internal: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:46:54Z" - latency: 7.651894ms message: 'load-balancer-api-internal: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:46:54Z" - latency: 54.474264ms message: 'load-balancer-api-internal: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 7.75671ms message: 'load-balancer-api-internal: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:45:54Z" - latency: 55.728616ms message: 'load-balancer-api-internal: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 7.73191ms message: 'load-balancer-api-internal: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:44:54Z" - latency: 49.258546ms message: 'load-balancer-api-internal: tcp connection to a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 7.146296ms message: 'load-balancer-api-internal: resolved host name a9e0eeeddb0cc409da088ac8135c41d1-80c4a411ee0df651.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:43:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-network-check-target-ip-10-0-131-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "173337" uid: 21a69498-0140-4bae-b104-a7957a96d09c spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T12:00:54Z" message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.604945ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 1.449903ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 1.292327ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 1.512099ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:42:54Z" - latency: 1.472487ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:41:54Z" - latency: 883.873µs message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:40:54Z" - latency: 898.716µs message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:39:54Z" - latency: 1.666663ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:38:54Z" - latency: 836.737µs message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:37:54Z" - latency: 1.874918ms message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:36:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-network-check-target-ip-10-0-136-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "173338" uid: 3f662095-d770-4637-9412-f8e28076d54b spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T12:00:54Z" message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.471849ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 2.701431ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 2.389138ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 2.357539ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:42:54Z" - latency: 2.456223ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:41:54Z" - latency: 2.598983ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:40:54Z" - latency: 2.647357ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:39:54Z" - latency: 2.734507ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:38:54Z" - latency: 2.631432ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:37:54Z" - latency: 2.689097ms message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:36:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-network-check-target-ip-10-0-139-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "173341" uid: f01272ae-9afb-4f07-ad8f-1abde0e2defc spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T12:00:54Z" message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.376379ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 2.386688ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 2.521459ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 2.271815ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:42:54Z" - latency: 2.227919ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:41:54Z" - latency: 2.634941ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:40:54Z" - latency: 2.207668ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:39:54Z" - latency: 2.584147ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:38:54Z" - latency: 2.172328ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:37:54Z" - latency: 2.33855ms message: 'network-check-target-ip-10-0-139-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:36:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T11:53:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-136-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-136.us-west-2.compute.internal uid: 69c247e8-e2cc-45d2-aa26-1c8935f70f2b resourceVersion: "174878" uid: f61a7550-8701-4cdc-8d8c-d2fb2e03e529 spec: sourcePod: network-check-source-6f78d59f99-fxq8l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T11:59:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.645293ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:47:54Z" - latency: 7.173839ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:47:54Z" - latency: 964.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:46:54Z" - latency: 2.413044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:46:54Z" - latency: 964.022µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:45:54Z" - latency: 2.477718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:45:54Z" - latency: 1.043297ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:44:54Z" - latency: 2.254758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:44:54Z" - latency: 908.462µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:43:54Z" - latency: 2.129894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:43:54Z" kind: List metadata: resourceVersion: ""