apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "70762" uid: 71f7d5f6-0131-4b07-b52c-f646312aec8b spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-25T01:23:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:05:28Z" - latency: 1.090626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 1.548559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 1.274681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 1.176143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 814.385µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 1.221273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:59:28Z" - latency: 1.27308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:58:28Z" - latency: 952.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:57:28Z" - latency: 1.384354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:56:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "68935" uid: 2c20557e-7c95-4870-962f-43b039de2b74 spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-25T01:22:28Z" message: 'load-balancer-api-external: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.46198ms message: 'load-balancer-api-external: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 8.515439ms message: 'load-balancer-api-external: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:04:28Z" - latency: 5.34828ms message: 'load-balancer-api-external: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 11.730185ms message: 'load-balancer-api-external: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:03:28Z" - latency: 4.824741ms message: 'load-balancer-api-external: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 7.846962ms message: 'load-balancer-api-external: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:02:28Z" - latency: 5.498085ms message: 'load-balancer-api-external: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 9.097081ms message: 'load-balancer-api-external: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:01:28Z" - latency: 4.581098ms message: 'load-balancer-api-external: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 8.86436ms message: 'load-balancer-api-external: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:00:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "68936" uid: 5d96eb07-7453-404b-a048-1564e51a8645 spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-25T01:22:28Z" message: 'load-balancer-api-internal: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.763626ms message: 'load-balancer-api-internal: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 8.492388ms message: 'load-balancer-api-internal: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:04:28Z" - latency: 6.136616ms message: 'load-balancer-api-internal: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 11.653574ms message: 'load-balancer-api-internal: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:03:28Z" - latency: 4.795051ms message: 'load-balancer-api-internal: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 7.898116ms message: 'load-balancer-api-internal: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:02:28Z" - latency: 5.43883ms message: 'load-balancer-api-internal: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 9.126885ms message: 'load-balancer-api-internal: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:01:28Z" - latency: 4.862186ms message: 'load-balancer-api-internal: tcp connection to ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 8.905989ms message: 'load-balancer-api-internal: resolved host name ac3eed6ed307b4148a1bb03a5b86619f-0cbd9b35fdba7be6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-25T02:00:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-network-check-target-ip-10-0-129-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "70760" uid: 7395ccda-6c13-4699-b4f2-56431e4c4de7 spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-25T01:23:28Z" message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.249387ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:05:28Z" - latency: 1.98861ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 2.199253ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 2.292309ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 2.34926ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 2.159148ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 2.359307ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:59:28Z" - latency: 2.351439ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:58:28Z" - latency: 2.08654ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:57:28Z" - latency: 1.989451ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:56:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-network-check-target-ip-10-0-129-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "70759" uid: c9147245-b748-4446-bb20-d8c69d1842fc spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-25T01:23:28Z" message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 869.649µs message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:05:28Z" - latency: 1.001038ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 1.001055ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 911.79µs message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 1.246332ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 1.096784ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 960.725µs message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:59:28Z" - latency: 1.70859ms message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:58:28Z" - latency: 941.641µs message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:57:28Z" - latency: 936.797µs message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:56:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-network-check-target-ip-10-0-135-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "70761" uid: 492326fa-db05-4746-a961-a1a13642d41f spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-25T01:23:28Z" message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.109357ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:05:28Z" - latency: 2.022578ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 2.455432ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 2.274081ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 2.101897ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 2.151943ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 2.374293ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:59:28Z" - latency: 2.375927ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:58:28Z" - latency: 2.012385ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:57:28Z" - latency: 2.250614ms message: 'network-check-target-ip-10-0-135-99: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-25T01:56:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-25T01:16:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-35.ec2.internal uid: e1067f5d-5c6b-4e7d-8ba3-8c32c4141cef resourceVersion: "68934" uid: b1fd8ac0-75c4-488b-ad90-25a68c21965c spec: sourcePod: network-check-source-7d88cb55d8-d4tds targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-25T01:22:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088323ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:04:28Z" - latency: 1.852216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:04:28Z" - latency: 1.175289ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:03:28Z" - latency: 2.075123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:03:28Z" - latency: 1.052469ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:02:28Z" - latency: 1.924916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:02:28Z" - latency: 1.080794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:01:28Z" - latency: 1.812354ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:01:28Z" - latency: 880.522µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-25T02:00:28Z" - latency: 2.092489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-25T02:00:28Z" kind: List metadata: resourceVersion: ""