apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "15125"
    uid: d4898d47-7f01-478d-8cca-9b3b6a3171f5
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:53:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:53:03Z"
    - latency: 913.958µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 985.97µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 1.318367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 1.107092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 1.070708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 1.300961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "14683"
    uid: 5ea146d5-59f4-4a3e-b1fb-cc8581c95c40
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:03Z"
      message: 'load-balancer-api-external: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.196431ms
      message: 'load-balancer-api-external: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 7.149216ms
      message: 'load-balancer-api-external: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 4.115958ms
      message: 'load-balancer-api-external: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 7.180367ms
      message: 'load-balancer-api-external: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 3.69077ms
      message: 'load-balancer-api-external: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 6.580107ms
      message: 'load-balancer-api-external: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 3.994938ms
      message: 'load-balancer-api-external: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 6.160895ms
      message: 'load-balancer-api-external: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 4.207388ms
      message: 'load-balancer-api-external: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 6.515797ms
      message: 'load-balancer-api-external: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:48:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "14684"
    uid: fedebcb8-1445-457d-b905-ee71d7f6045c
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:03Z"
      message: 'load-balancer-api-internal: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.171358ms
      message: 'load-balancer-api-internal: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 7.220229ms
      message: 'load-balancer-api-internal: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 4.251783ms
      message: 'load-balancer-api-internal: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 7.28292ms
      message: 'load-balancer-api-internal: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 3.676361ms
      message: 'load-balancer-api-internal: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 6.555074ms
      message: 'load-balancer-api-internal: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 4.00128ms
      message: 'load-balancer-api-internal: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 6.144934ms
      message: 'load-balancer-api-internal: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 4.206715ms
      message: 'load-balancer-api-internal: tcp connection to ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 6.533817ms
      message: 'load-balancer-api-internal: resolved host name ab7a68a3be2a346c7b21283bc9272bee-670563109f25c873.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:48:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-130-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "15123"
    uid: e5d0b55d-5177-4b0d-b055-6eb708748cac
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:53:03Z"
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.486541ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:53:03Z"
    - latency: 2.505043ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 2.387585ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 2.109372ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 2.541152ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 2.277244ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 2.178871ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-133-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "15122"
    uid: 5700b9d7-f22d-4747-9564-1a67a5dda711
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:53:03Z"
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.239547ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:53:03Z"
    - latency: 878.985µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 1.032002ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 1.177634ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 1.081594ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 996.563µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 1.10107ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-136-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "15124"
    uid: d6669280-3ee1-4692-a0a6-2fea40347934
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:53:03Z"
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.73415ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:53:03Z"
    - latency: 2.569396ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 3.046971ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 2.502167ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 2.421752ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 2.209055ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 2.23883ms
      message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T02:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 24231e69-2b30-4814-8d15-135de8e70bad
    resourceVersion: "14682"
    uid: add5d66d-26a6-4f66-8582-da482672fd03
  spec:
    sourcePod: network-check-source-685456655f-cglm5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T02:52:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 1.823172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:52:03Z"
    - latency: 1.000033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 1.71083ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:51:03Z"
    - latency: 866.954µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 2.123747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:50:03Z"
    - latency: 1.028428ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 1.781873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:49:03Z"
    - latency: 960.782µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T02:48:03Z"
    - latency: 1.926632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T02:48:03Z"
kind: List
metadata:
  resourceVersion: ""