apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "70760" uid: 157ced3a-d4b0-4ea9-b2cd-08a63a719255 spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-01T00:38:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.433366ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:20:56Z" - latency: 1.315054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:19:56Z" - latency: 1.319722ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:18:56Z" - latency: 1.045177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:17:56Z" - latency: 1.315708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:16:56Z" - latency: 1.322827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:15:56Z" - latency: 1.0125ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:14:56Z" - latency: 1.103403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:13:56Z" - latency: 1.120223ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:12:56Z" - latency: 949.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:11:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "76501" uid: f75cecb5-2965-436f-b8b0-647c01c0b2d1 spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-01T00:37:56Z" message: 'load-balancer-api-external: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.426351ms message: 'load-balancer-api-external: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:25:56Z" - latency: 7.493873ms message: 'load-balancer-api-external: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:25:56Z" - latency: 4.257507ms message: 'load-balancer-api-external: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:24:56Z" - latency: 6.620558ms message: 'load-balancer-api-external: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:24:56Z" - latency: 4.665269ms message: 'load-balancer-api-external: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:23:56Z" - latency: 7.502873ms message: 'load-balancer-api-external: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:23:56Z" - latency: 4.77693ms message: 'load-balancer-api-external: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:22:56Z" - latency: 7.836386ms message: 'load-balancer-api-external: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:22:56Z" - latency: 3.961894ms message: 'load-balancer-api-external: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:21:56Z" - latency: 6.099512ms message: 'load-balancer-api-external: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "76502" uid: f7278a96-226e-44da-90f4-e47075abdfe8 spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-01T00:37:56Z" message: 'load-balancer-api-internal: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.474084ms message: 'load-balancer-api-internal: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:25:56Z" - latency: 7.538602ms message: 'load-balancer-api-internal: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:25:56Z" - latency: 4.984738ms message: 'load-balancer-api-internal: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:24:56Z" - latency: 6.701314ms message: 'load-balancer-api-internal: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:24:56Z" - latency: 4.116511ms message: 'load-balancer-api-internal: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:23:56Z" - latency: 7.580318ms message: 'load-balancer-api-internal: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:23:56Z" - latency: 4.720113ms message: 'load-balancer-api-internal: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:22:56Z" - latency: 7.79874ms message: 'load-balancer-api-internal: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:22:56Z" - latency: 3.612977ms message: 'load-balancer-api-internal: tcp connection to a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:21:56Z" - latency: 6.171095ms message: 'load-balancer-api-internal: resolved host name a6d9e1c504d774cb08cb544eb9a2713f-eb77f5013ea21560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-01T01:21:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-network-check-target-ip-10-0-128-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "70758" uid: d117af96-ab01-4490-aef2-5aa873bc8e45 spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-01T00:38:56Z" message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.454841ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:20:56Z" - latency: 2.441739ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:19:56Z" - latency: 2.232483ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:18:56Z" - latency: 2.023006ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:17:56Z" - latency: 2.610152ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:16:56Z" - latency: 2.761204ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:15:56Z" - latency: 2.689477ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:14:56Z" - latency: 2.739933ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:13:56Z" - latency: 2.031253ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:12:56Z" - latency: 2.100785ms message: 'network-check-target-ip-10-0-128-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:11:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-network-check-target-ip-10-0-131-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "70757" uid: 1e8bb4a2-7730-4bad-9ead-7f8f199d9984 spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-01T00:38:56Z" message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.020559ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:20:56Z" - latency: 1.082995ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:19:56Z" - latency: 1.086168ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:18:56Z" - latency: 1.043731ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:17:56Z" - latency: 1.054835ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:16:56Z" - latency: 1.128374ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:15:56Z" - latency: 1.265009ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:14:56Z" - latency: 1.085381ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:13:56Z" - latency: 891.114µs message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:12:56Z" - latency: 1.037948ms message: 'network-check-target-ip-10-0-131-26: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:11:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-network-check-target-ip-10-0-140-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "70759" uid: 16d0e94f-8fad-4dc2-80a7-0c6c0592a82f spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-01T00:38:56Z" message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.593917ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:20:56Z" - latency: 2.468076ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:19:56Z" - latency: 2.446354ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:18:56Z" - latency: 2.254016ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:17:56Z" - latency: 2.501074ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:16:56Z" - latency: 2.444709ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:15:56Z" - latency: 2.599663ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:14:56Z" - latency: 2.265645ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:13:56Z" - latency: 2.474411ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:12:56Z" - latency: 2.205802ms message: 'network-check-target-ip-10-0-140-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:11:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-01T00:31:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-26-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-26.ec2.internal uid: 7bed4bfa-02a1-477c-9e9a-624363b1920e resourceVersion: "76500" uid: 4ef9f05e-8fd4-4089-ac86-923339a8d437 spec: sourcePod: network-check-source-65bdbbff45-bghcv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-01T00:37:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.417µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:25:56Z" - latency: 2.686943ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:25:56Z" - latency: 935.641µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:24:56Z" - latency: 1.7447ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:24:56Z" - latency: 898.826µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:23:56Z" - latency: 2.125003ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:23:56Z" - latency: 927.874µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:22:56Z" - latency: 2.760511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:22:56Z" - latency: 1.075619ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-01T01:21:56Z" - latency: 1.72739ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-01T01:21:56Z" kind: List metadata: resourceVersion: ""