apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61191" uid: df503534-ed00-4f2e-9e10-d0448790d638 spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T17:15:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.112µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 1.271996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 1.100564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 1.628676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 1.15082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 1.200892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:45:12Z" - latency: 1.403894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:44:12Z" - latency: 1.157146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:43:12Z" - latency: 1.025638ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:42:12Z" - latency: 1.28535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:41:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61193" uid: 01e766cf-0459-4c4e-a73b-cf807d1a5621 spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T17:14:12Z" message: 'load-balancer-api-external: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.144126ms message: 'load-balancer-api-external: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 6.96598ms message: 'load-balancer-api-external: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:50:12Z" - latency: 3.849924ms message: 'load-balancer-api-external: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 8.384977ms message: 'load-balancer-api-external: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:49:12Z" - latency: 4.81835ms message: 'load-balancer-api-external: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 9.394967ms message: 'load-balancer-api-external: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:48:12Z" - latency: 3.961874ms message: 'load-balancer-api-external: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 7.446868ms message: 'load-balancer-api-external: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:47:12Z" - latency: 5.935039ms message: 'load-balancer-api-external: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 8.92312ms message: 'load-balancer-api-external: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:46:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61192" uid: 9e2c3139-0d0a-428b-9c36-9dac9fa1c74f spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T17:14:12Z" message: 'load-balancer-api-internal: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.3711ms message: 'load-balancer-api-internal: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 6.94683ms message: 'load-balancer-api-internal: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:50:12Z" - latency: 3.766922ms message: 'load-balancer-api-internal: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 8.372507ms message: 'load-balancer-api-internal: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:49:12Z" - latency: 8.114344ms message: 'load-balancer-api-internal: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 9.334794ms message: 'load-balancer-api-internal: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:48:12Z" - latency: 3.866087ms message: 'load-balancer-api-internal: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 7.367404ms message: 'load-balancer-api-internal: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:47:12Z" - latency: 5.505225ms message: 'load-balancer-api-internal: tcp connection to a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 8.975835ms message: 'load-balancer-api-internal: resolved host name a53f390bc9a8e483eb32e78cf014a865-0e1ea29df50d4273.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T17:46:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-network-check-target-ip-10-0-128-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61187" uid: 28a79f0f-dc13-4217-8ea1-abafbe9fada4 spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T17:15:12Z" message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.136028ms message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 990.95µs message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 1.156927ms message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 1.066975ms message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 947.061µs message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 985.059µs message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:45:12Z" - latency: 1.49512ms message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:44:12Z" - latency: 905.741µs message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:43:12Z" - latency: 947.784µs message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:42:12Z" - latency: 933.805µs message: 'network-check-target-ip-10-0-128-240: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:41:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-network-check-target-ip-10-0-129-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61188" uid: 81577821-be21-4f70-9380-e3a328ada636 spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T17:15:12Z" message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.2732ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 2.486491ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 2.972554ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 2.756642ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 2.641336ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 2.58911ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:45:12Z" - latency: 2.220177ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:44:12Z" - latency: 2.368549ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:43:12Z" - latency: 2.202563ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:42:12Z" - latency: 2.340965ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:41:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-network-check-target-ip-10-0-137-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61190" uid: fc97f5df-2fb5-43f9-a547-9ece617d7929 spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T17:15:12Z" message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.35656ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 2.587426ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 2.966171ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 2.664605ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 2.805085ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 2.94503ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:45:12Z" - latency: 2.508336ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:44:12Z" - latency: 3.167478ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:43:12Z" - latency: 2.190455ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:42:12Z" - latency: 2.197373ms message: 'network-check-target-ip-10-0-137-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:41:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T17:08:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-240-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-240.ec2.internal uid: 8545b64c-9ed7-4cf4-ad69-5773d9595492 resourceVersion: "61189" uid: ba781c20-9919-4743-bf87-238d5faf472f spec: sourcePod: network-check-source-869dcfcdcd-2mrxl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T17:14:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.254µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:50:12Z" - latency: 1.874055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:50:12Z" - latency: 869.321µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:49:12Z" - latency: 1.860175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:49:12Z" - latency: 728.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:48:12Z" - latency: 1.96856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:48:12Z" - latency: 1.547913ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:47:12Z" - latency: 2.224672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:47:12Z" - latency: 912.443µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T17:46:12Z" - latency: 1.822935ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T17:46:12Z" kind: List metadata: resourceVersion: ""