apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "54774" uid: 9545dc68-9e99-4e4a-948b-16077f61026f spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T22:34:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.547617ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 1.073668ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 904.088µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 1.086869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 1.532005ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:05Z" - latency: 1.101695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:05Z" - latency: 1.218064ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:05Z" - latency: 1.266781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:55:05Z" - latency: 1.117325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:54:05Z" - latency: 1.082947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "55741" uid: 5c217731-defd-402c-bdd2-c2c870a00688 spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T22:33:05Z" message: 'load-balancer-api-external: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.439093ms message: 'load-balancer-api-external: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:05Z" - latency: 7.252696ms message: 'load-balancer-api-external: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:03:05Z" - latency: 3.663492ms message: 'load-balancer-api-external: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 8.535153ms message: 'load-balancer-api-external: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:02:05Z" - latency: 4.672034ms message: 'load-balancer-api-external: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 6.998365ms message: 'load-balancer-api-external: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:01:05Z" - latency: 5.506843ms message: 'load-balancer-api-external: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 7.7184ms message: 'load-balancer-api-external: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:00:05Z" - latency: 4.787294ms message: 'load-balancer-api-external: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 7.268957ms message: 'load-balancer-api-external: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:59:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "55740" uid: 4019a155-59ab-47a7-9770-20329c6274ad spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T22:33:05Z" message: 'load-balancer-api-internal: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.411932ms message: 'load-balancer-api-internal: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:05Z" - latency: 7.065997ms message: 'load-balancer-api-internal: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:03:05Z" - latency: 4.254847ms message: 'load-balancer-api-internal: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 8.493463ms message: 'load-balancer-api-internal: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:02:05Z" - latency: 5.180519ms message: 'load-balancer-api-internal: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 6.915216ms message: 'load-balancer-api-internal: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:01:05Z" - latency: 3.148649ms message: 'load-balancer-api-internal: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 7.870525ms message: 'load-balancer-api-internal: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:00:05Z" - latency: 4.783773ms message: 'load-balancer-api-internal: tcp connection to a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 7.221623ms message: 'load-balancer-api-internal: resolved host name a418449d1c57340d3bf5133650d1e8cc-8ca78d17fe49cfda.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T22:59:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-network-check-target-ip-10-0-130-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "54772" uid: 7cfdc8af-0e7a-44e7-95a4-ba5535c4bbb2 spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:34:05Z" message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.43595ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 2.303769ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 2.345947ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 2.516243ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 2.502055ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:05Z" - latency: 2.507913ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:05Z" - latency: 2.597583ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:05Z" - latency: 2.500611ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:55:05Z" - latency: 2.403458ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:54:05Z" - latency: 2.426301ms message: 'network-check-target-ip-10-0-130-224: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-network-check-target-ip-10-0-132-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "54773" uid: 9129f589-533a-4618-b96c-a430ac3474d7 spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:34:05Z" message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.754693ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 2.463164ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 2.324281ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 2.303439ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 2.73389ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:05Z" - latency: 2.482142ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:05Z" - latency: 2.697438ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:05Z" - latency: 2.65729ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:55:05Z" - latency: 2.334581ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:54:05Z" - latency: 2.020554ms message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-network-check-target-ip-10-0-135-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "54771" uid: 77455532-ab59-438b-bb54-a2a4b9292601 spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:34:05Z" message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.224753ms message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 979.266µs message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 1.550432ms message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 1.014399ms message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 1.929637ms message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:05Z" - latency: 880.707µs message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:05Z" - latency: 1.613745ms message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:05Z" - latency: 911.416µs message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:55:05Z" - latency: 933.656µs message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:54:05Z" - latency: 1.591867ms message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:53:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-55-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-55.ec2.internal uid: f6701fe0-9d1d-4d3f-9185-4f0cc900fd6c resourceVersion: "55738" uid: 8909a2bf-2898-4165-8d43-c81ca71dfaec spec: sourcePod: network-check-source-989f8b8dc-s57dw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T22:33:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.781µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:05Z" - latency: 1.755273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:03:05Z" - latency: 846.773µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:05Z" - latency: 2.038384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:02:05Z" - latency: 878.074µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:05Z" - latency: 1.723052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:01:05Z" - latency: 902.543µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:05Z" - latency: 2.184027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:00:05Z" - latency: 823.194µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:05Z" - latency: 1.847215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T22:59:05Z" kind: List metadata: resourceVersion: ""