apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "15020"
    uid: dd515940-23e6-4bd8-84f3-24f246bba808
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:25:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:19Z"
    - latency: 927.08µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 1.194516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 1.010825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 918.279µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 1.793229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 1.017603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "14619"
    uid: a957c560-9fe6-4a39-9753-9c9bcafc82f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:24:19Z"
      message: 'load-balancer-api-external: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.572141ms
      message: 'load-balancer-api-external: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 8.075116ms
      message: 'load-balancer-api-external: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 6.069801ms
      message: 'load-balancer-api-external: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 9.486375ms
      message: 'load-balancer-api-external: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 6.162948ms
      message: 'load-balancer-api-external: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 8.188122ms
      message: 'load-balancer-api-external: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 6.173739ms
      message: 'load-balancer-api-external: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 9.636711ms
      message: 'load-balancer-api-external: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 5.944695ms
      message: 'load-balancer-api-external: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 9.175284ms
      message: 'load-balancer-api-external: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:20:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "14618"
    uid: 9789dceb-37b5-4515-a283-0ff054a537e1
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:24:19Z"
      message: 'load-balancer-api-internal: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.558323ms
      message: 'load-balancer-api-internal: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 8.105794ms
      message: 'load-balancer-api-internal: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 6.575132ms
      message: 'load-balancer-api-internal: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 9.446766ms
      message: 'load-balancer-api-internal: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 6.151963ms
      message: 'load-balancer-api-internal: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 8.1378ms
      message: 'load-balancer-api-internal: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 4.60576ms
      message: 'load-balancer-api-internal: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 9.597706ms
      message: 'load-balancer-api-internal: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 5.960923ms
      message: 'load-balancer-api-internal: tcp connection to a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 9.224115ms
      message: 'load-balancer-api-internal: resolved host name a23da8a19b5fc4a5a8a2d77d907cab5e-69af93953c6d96eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:20:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-ip-10-0-131-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "15017"
    uid: bd1a9f4d-d770-4439-a0e2-7193078be477
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:25:19Z"
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.016825ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:19Z"
    - latency: 2.353787ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 1.898512ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 1.762815ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 1.92593ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 2.125ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 2.025482ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-ip-10-0-133-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "15018"
    uid: e5b8b6b8-a246-4ae9-93db-94fc75b6dfda
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:25:19Z"
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.089µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:19Z"
    - latency: 751.7µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 787.743µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 711.978µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 860.787µs
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 1.96314ms
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 1.477334ms
      message: 'network-check-target-ip-10-0-133-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-ip-10-0-137-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "15019"
    uid: b53847fc-66cf-4109-872d-b3a8b3f2c609
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:25:19Z"
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.936362ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:19Z"
    - latency: 2.006533ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 2.104112ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 2.135435ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 2.10722ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 2.212214ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 2.328175ms
      message: 'network-check-target-ip-10-0-137-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:18:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-184-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-184.ec2.internal
      uid: 0f7f580a-617b-4ed3-97d9-f52cec1b609e
    resourceVersion: "14616"
    uid: 9275c65e-3ba5-440a-94d5-85010900a687
  spec:
    sourcePod: network-check-source-7cbc45fddc-cfz7z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:24:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 779.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 2.026789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:19Z"
    - latency: 817.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 1.944053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:23:19Z"
    - latency: 1.18331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 1.724352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:22:19Z"
    - latency: 1.032219ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 1.662373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:21:19Z"
    - latency: 829.579µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:19Z"
    - latency: 2.463524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:20:19Z"
kind: List
metadata:
  resourceVersion: ""