apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14726"
    uid: 79e6e6bf-2688-4f70-ab26-b2e704a94eb3
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:57:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 821.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:00Z"
    - latency: 999.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 1.108027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 841.579µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 1.008448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 951.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 1.515386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:51:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14399"
    uid: 00be0c85-ea15-48c1-8bf4-65854ac71b10
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:56:00Z"
      message: 'load-balancer-api-external: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.918106ms
      message: 'load-balancer-api-external: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 8.342976ms
      message: 'load-balancer-api-external: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 5.63147ms
      message: 'load-balancer-api-external: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 6.919626ms
      message: 'load-balancer-api-external: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 4.76966ms
      message: 'load-balancer-api-external: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 6.835308ms
      message: 'load-balancer-api-external: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 4.15198ms
      message: 'load-balancer-api-external: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 12.611254ms
      message: 'load-balancer-api-external: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 4.5626ms
      message: 'load-balancer-api-external: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 8.073445ms
      message: 'load-balancer-api-external: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14398"
    uid: c8818544-79db-48db-a01b-ed1e15028410
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:56:00Z"
      message: 'load-balancer-api-internal: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.881266ms
      message: 'load-balancer-api-internal: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 8.447782ms
      message: 'load-balancer-api-internal: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 6.013258ms
      message: 'load-balancer-api-internal: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 7.034245ms
      message: 'load-balancer-api-internal: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 4.515627ms
      message: 'load-balancer-api-internal: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 6.926155ms
      message: 'load-balancer-api-internal: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 4.947444ms
      message: 'load-balancer-api-internal: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 12.637947ms
      message: 'load-balancer-api-internal: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 4.493027ms
      message: 'load-balancer-api-internal: tcp connection to a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 8.143488ms
      message: 'load-balancer-api-internal: resolved host name a1738916a74b94a1b90a6d61a88d00cf-4b934696dfe98beb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:52:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-network-check-target-ip-10-0-133-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14723"
    uid: 5ea78505-318e-484a-89d1-6359873a20cf
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:57:00Z"
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.299µs
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:00Z"
    - latency: 945.863µs
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 1.27621ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 818.504µs
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 781.672µs
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 923.793µs
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 1.54304ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:51:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-network-check-target-ip-10-0-141-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14724"
    uid: 08566ec5-a904-4b55-8ec1-40916cf04c1b
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:57:00Z"
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.860092ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:00Z"
    - latency: 1.697209ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 2.088283ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 1.975951ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 1.857061ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 1.842029ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 2.130765ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:51:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-network-check-target-ip-10-0-142-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14725"
    uid: bf88f93d-7d8e-406e-90a5-5f2a6ca91871
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:57:00Z"
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.145987ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:57:00Z"
    - latency: 1.769718ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 2.072601ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 2.149833ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 2.102096ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 2.534761ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 2.227173ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:51:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T13:49:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-136-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-136.ec2.internal
      uid: 0ad0e5b8-0d78-4d6f-9030-6c01db588444
    resourceVersion: "14397"
    uid: b5ce9d63-3b9b-4a1d-8800-fb23e3ea539d
  spec:
    sourcePod: network-check-source-7d88cb55d8-9jr4n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:56:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 804.579µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 1.71165ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:56:00Z"
    - latency: 1.106595ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 1.732538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:55:00Z"
    - latency: 915.815µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 1.832161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:54:00Z"
    - latency: 1.020076ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 2.028713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:53:00Z"
    - latency: 973.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:52:00Z"
    - latency: 1.802258ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:52:00Z"
kind: List
metadata:
  resourceVersion: ""