apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "14761"
    uid: 88a2dd2c-187d-4057-a35b-0cf36586db7a
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:44:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.087µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:44:18Z"
    - latency: 1.296928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:43:18Z"
    - latency: 946.419µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:42:18Z"
    - latency: 1.201053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:41:18Z"
    - latency: 1.008358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:40:18Z"
    - latency: 1.064931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:39:18Z"
    - latency: 881.75µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:38:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "16647"
    uid: 5cd42760-fd11-4d86-bd76-048976c2f93e
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:43:18Z"
      message: 'load-balancer-api-external: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.204195ms
      message: 'load-balancer-api-external: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:49:18Z"
    - latency: 9.750731ms
      message: 'load-balancer-api-external: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:49:18Z"
    - latency: 5.625714ms
      message: 'load-balancer-api-external: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:48:18Z"
    - latency: 9.394747ms
      message: 'load-balancer-api-external: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:48:18Z"
    - latency: 4.442559ms
      message: 'load-balancer-api-external: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:47:18Z"
    - latency: 9.326178ms
      message: 'load-balancer-api-external: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:47:18Z"
    - latency: 6.153491ms
      message: 'load-balancer-api-external: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:46:18Z"
    - latency: 9.081955ms
      message: 'load-balancer-api-external: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:46:18Z"
    - latency: 6.200638ms
      message: 'load-balancer-api-external: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:45:18Z"
    - latency: 8.321992ms
      message: 'load-balancer-api-external: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "16646"
    uid: 89ef2a36-67e8-4942-b072-3ef2ad4569b6
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:43:18Z"
      message: 'load-balancer-api-internal: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.180151ms
      message: 'load-balancer-api-internal: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:49:18Z"
    - latency: 10.052884ms
      message: 'load-balancer-api-internal: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:49:18Z"
    - latency: 5.651385ms
      message: 'load-balancer-api-internal: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:48:18Z"
    - latency: 9.174703ms
      message: 'load-balancer-api-internal: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:48:18Z"
    - latency: 4.494989ms
      message: 'load-balancer-api-internal: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:47:18Z"
    - latency: 9.299444ms
      message: 'load-balancer-api-internal: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:47:18Z"
    - latency: 6.129788ms
      message: 'load-balancer-api-internal: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:46:18Z"
    - latency: 9.024763ms
      message: 'load-balancer-api-internal: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:46:18Z"
    - latency: 6.747528ms
      message: 'load-balancer-api-internal: tcp connection to ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:45:18Z"
    - latency: 8.291578ms
      message: 'load-balancer-api-internal: resolved host name ad81da4fc64f04916832bf259578ad23-1ab4cb49cac1ffc3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:45:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-135-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "14759"
    uid: abf0e531-6392-4210-8a69-3437439c86be
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:44:18Z"
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.626µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:44:18Z"
    - latency: 1.063516ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:43:18Z"
    - latency: 872.864µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:42:18Z"
    - latency: 1.040359ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:41:18Z"
    - latency: 955.036µs
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:40:18Z"
    - latency: 1.379746ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:39:18Z"
    - latency: 1.049104ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:38:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-136-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "14758"
    uid: 96eb942f-f82c-41e1-b8e6-a671301e0776
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:44:18Z"
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.974104ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:44:18Z"
    - latency: 1.962406ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:43:18Z"
    - latency: 2.221407ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:42:18Z"
    - latency: 2.291185ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:41:18Z"
    - latency: 1.974216ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:40:18Z"
    - latency: 2.204636ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:39:18Z"
    - latency: 1.879025ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:38:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-142-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "14760"
    uid: f5b6cd3d-9ca1-43ac-85d5-f4c01a751bfc
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:44:18Z"
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.117136ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:44:18Z"
    - latency: 2.273879ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:43:18Z"
    - latency: 5.940929ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:42:18Z"
    - latency: 2.325328ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:41:18Z"
    - latency: 2.172709ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:40:18Z"
    - latency: 2.237138ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:39:18Z"
    - latency: 2.134233ms
      message: 'network-check-target-ip-10-0-142-177: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:38:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T15:37:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-205.ec2.internal
      uid: e5b3a536-6985-44d9-827d-00e349ad24e6
    resourceVersion: "16645"
    uid: 54729012-5ef2-402c-bb0e-316ebe53a1d3
  spec:
    sourcePod: network-check-source-65bdbbff45-f77mw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T15:43:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082513ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:49:18Z"
    - latency: 2.411994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:49:18Z"
    - latency: 847.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:48:18Z"
    - latency: 1.964859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:48:18Z"
    - latency: 867.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:47:18Z"
    - latency: 2.28841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:47:18Z"
    - latency: 951.519µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:46:18Z"
    - latency: 2.412279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:46:18Z"
    - latency: 1.203976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T15:45:18Z"
    - latency: 1.698553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T15:45:18Z"
kind: List
metadata:
  resourceVersion: ""