apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "15015"
    uid: b49ec4c9-475c-4992-81a5-a224a6bd8ae5
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:59:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.124272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:59:22Z"
    - latency: 1.334196ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 995.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 1.04872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 1.51446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 883.215µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 1.056263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:53:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "14575"
    uid: 048dbea0-7117-4a69-8795-46eff992b708
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:58:22Z"
      message: 'load-balancer-api-external: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.674193ms
      message: 'load-balancer-api-external: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 6.898951ms
      message: 'load-balancer-api-external: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 4.8344ms
      message: 'load-balancer-api-external: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 10.753952ms
      message: 'load-balancer-api-external: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 3.792856ms
      message: 'load-balancer-api-external: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 8.369284ms
      message: 'load-balancer-api-external: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 5.884598ms
      message: 'load-balancer-api-external: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 8.170204ms
      message: 'load-balancer-api-external: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 4.747002ms
      message: 'load-balancer-api-external: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 9.696266ms
      message: 'load-balancer-api-external: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:54:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "14576"
    uid: 06983112-ccc7-4c70-a033-e85b693417b1
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:58:22Z"
      message: 'load-balancer-api-internal: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.66194ms
      message: 'load-balancer-api-internal: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 6.773247ms
      message: 'load-balancer-api-internal: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 5.063862ms
      message: 'load-balancer-api-internal: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 10.706499ms
      message: 'load-balancer-api-internal: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 5.102674ms
      message: 'load-balancer-api-internal: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 8.228786ms
      message: 'load-balancer-api-internal: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 5.222656ms
      message: 'load-balancer-api-internal: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 8.139425ms
      message: 'load-balancer-api-internal: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 4.752776ms
      message: 'load-balancer-api-internal: tcp connection to a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 9.785897ms
      message: 'load-balancer-api-internal: resolved host name a31bf605985e9414499491adba8674b2-a07bb631231b5fef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:54:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-network-check-target-ip-10-0-129-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "15013"
    uid: 04fb3669-a74a-405f-8b25-bad3e317dfd5
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:59:22Z"
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.948659ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:59:22Z"
    - latency: 2.250892ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 2.142336ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 2.434794ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 2.386808ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 2.191267ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 2.568262ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:53:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-network-check-target-ip-10-0-140-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "15012"
    uid: d516ad09-14bb-4a1c-9dc4-2c365f4e9c8b
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:59:22Z"
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.906µs
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:59:22Z"
    - latency: 1.009383ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 1.022833ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 973.296µs
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 1.083123ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 798.779µs
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 1.57149ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:53:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-network-check-target-ip-10-0-140-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "15014"
    uid: bea59c09-f99d-4fda-a8fe-545e2994300b
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:59:22Z"
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.28325ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:59:22Z"
    - latency: 2.367619ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 2.250426ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 2.06538ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 2.333201ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 2.144955ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 2.155544ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:53:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T16:52:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-127-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-127.ec2.internal
      uid: 8907c920-f052-4f6a-ba37-f09542f41260
    resourceVersion: "14574"
    uid: 19711bc3-0219-44b9-92d5-4d60459b9f12
  spec:
    sourcePod: network-check-source-65bdbbff45-pnlnq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T16:58:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.459241ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 1.855302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:58:22Z"
    - latency: 798.299µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 1.701799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:57:22Z"
    - latency: 822.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 2.125277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:56:22Z"
    - latency: 902.687µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 1.643502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:55:22Z"
    - latency: 880.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T16:54:22Z"
    - latency: 1.887027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T16:54:22Z"
kind: List
metadata:
  resourceVersion: ""