apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "56151" uid: ba6bb5e7-ef0a-4905-b993-76c7b63ddc22 spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T01:13:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.250303ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 1.105924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 854.592µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 982.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 888.793µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:37:39Z" - latency: 883.915µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:36:39Z" - latency: 1.293459ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:35:39Z" - latency: 908.853µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:34:39Z" - latency: 1.27441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:33:39Z" - latency: 819.534µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:32:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "57140" uid: 82fdfe2c-6af2-4362-90a1-90010cdee135 spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T01:12:39Z" message: 'load-balancer-api-external: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.903883ms message: 'load-balancer-api-external: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:42:39Z" - latency: 8.58051ms message: 'load-balancer-api-external: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:42:39Z" - latency: 4.299683ms message: 'load-balancer-api-external: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 12.105973ms message: 'load-balancer-api-external: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:41:39Z" - latency: 3.601151ms message: 'load-balancer-api-external: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 8.5416ms message: 'load-balancer-api-external: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:40:39Z" - latency: 3.71641ms message: 'load-balancer-api-external: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 8.508593ms message: 'load-balancer-api-external: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:39:39Z" - latency: 3.787841ms message: 'load-balancer-api-external: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 8.453655ms message: 'load-balancer-api-external: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:38:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "57141" uid: 5eebb83e-b971-4415-97ae-e7fb16cc4da3 spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T01:12:39Z" message: 'load-balancer-api-internal: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.732758ms message: 'load-balancer-api-internal: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:42:39Z" - latency: 8.630192ms message: 'load-balancer-api-internal: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:42:39Z" - latency: 4.486789ms message: 'load-balancer-api-internal: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 12.081278ms message: 'load-balancer-api-internal: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:41:39Z" - latency: 3.623782ms message: 'load-balancer-api-internal: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 8.594871ms message: 'load-balancer-api-internal: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:40:39Z" - latency: 4.534845ms message: 'load-balancer-api-internal: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 8.473751ms message: 'load-balancer-api-internal: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:39:39Z" - latency: 3.831832ms message: 'load-balancer-api-internal: tcp connection to a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 8.413037ms message: 'load-balancer-api-internal: resolved host name a0d8a06705c2b4412980e46c6812ba7f-8d7dfe0273282fca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T01:38:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-network-check-target-ip-10-0-131-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "56148" uid: cf760d10-0b8f-431f-b078-a329361aafd2 spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T01:13:39Z" message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.787µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 804.392µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 1.315382ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 860.053µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 987.77µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:37:39Z" - latency: 1.24658ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:36:39Z" - latency: 924.251µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:35:39Z" - latency: 946.278µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:34:39Z" - latency: 924.806µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:33:39Z" - latency: 745.469µs message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:32:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-network-check-target-ip-10-0-135-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "56150" uid: 60a878dd-e37f-4415-918a-b0883c3ec08f spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T01:13:39Z" message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.405223ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 2.347905ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 2.200158ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 2.359395ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 2.519402ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:37:39Z" - latency: 2.298275ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:36:39Z" - latency: 2.127105ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:35:39Z" - latency: 2.597336ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:34:39Z" - latency: 2.327907ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:33:39Z" - latency: 2.122908ms message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:32:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-network-check-target-ip-10-0-141-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "56149" uid: d5203798-be63-4a30-929a-e9f2fb909c8a spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T01:13:39Z" message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.294954ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 2.380863ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 2.431324ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 2.311813ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 2.464486ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:37:39Z" - latency: 2.187274ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:36:39Z" - latency: 2.252604ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:35:39Z" - latency: 2.411051ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:34:39Z" - latency: 2.303613ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:33:39Z" - latency: 2.08505ms message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:32:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T01:06:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-116-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-116.ec2.internal uid: 79eb0877-8084-47fe-ac46-1da16355cd8f resourceVersion: "57139" uid: 1ff0787a-77da-4ef2-b347-742db13dcaaf spec: sourcePod: network-check-source-989f8b8dc-ndpnj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T01:12:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 820.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:42:39Z" - latency: 1.670095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:42:39Z" - latency: 1.017156ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:41:39Z" - latency: 2.283609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:41:39Z" - latency: 865.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:40:39Z" - latency: 2.044487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:40:39Z" - latency: 833.038µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:39:39Z" - latency: 1.877922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:39:39Z" - latency: 936.407µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T01:38:39Z" - latency: 1.607036ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T01:38:39Z" kind: List metadata: resourceVersion: ""