This message was deleted.
# general
a
This message was deleted.
s
there's no
Continuous Delivery
icon in your sidenav?
a
yup
gone missing
fleet and continuous delivery feature flags are active
s
your user must have permissions to see the
fleet.cattle.io.gitrepo
resource, and the
continuous-delivery
feature flag must be enabled in order to see the menu item. can you check
<rancher url>/v1/schemas/fleet.cattle.io.gitrepo
and
<rancher url>/v3/features/continuous-delivery
return successfully?
a
{ • "type": "error", • "links": { }, • "code": "NotFound", • "message": "no such schema", • "status": 404 }
{ • "baseType": "feature", • "created": "2023-09-21T051457Z", • "createdTS": 1695273297000, • "creatorId": null, • "id": "continuous-delivery", • "links": { ◦ "remove": "…/v3/features/continuous-delivery", ◦ "self": "…/v3/features/continuous-delivery", ◦ "update": "…/v3/features/continuous-delivery" • }, • "name": "continuous-delivery", • "state": "active", • "status": { ◦ "default": true, ◦ "description": "Gitops components in fleet", ◦ "dynamic": false, ◦ "lockedValue": null, ◦ "type": "/v3/schemas/featureStatus" • }, • "transitioning": "no", • "transitioningMessage": "", • "type": "feature", • "uuid": "ff43bfe9-2575-4ad1-9533-9b0e3db42d29", • "value": true }
s
ok, your user cannot see a required fleet resource. that might be due to permissions, or maybe fleet has been removed form the upstream cluster
a
I fear fleet is not running
but I don't know why
s
if you navigate to your
local
cluster -->
Apps
/
Installed Apps
page you should see two in the
cattle-fleet-system
namespace. they should be able to provide more information. from there, probably worth asking in #fleet
a
I see maybe I know why
cattle-cluster-agent is not fully deployed
it keeps connecting and getting host cannot be resolved on one node
ERROR: https://**/ping is not accessible (Could not resolve host: **)
n
but only on one node, which is weird
so I have rancher which seems fine, agent is on the other cluster which troubles me, but is connected...
on Fleet it says that no cluster is ready
made it work, after some tinkering with server settings (kernel) and restart
👍 1