Old MeshSync CRD not handled #422
Description
Description
Meshery Operator was reinstalled on the Playground environment, because MeshSync wasn't running. The Operator had this log:
"meshery","name":"meshery-broker","reconcileID":"fe61be5b-3cd8-4cab-b171-34cd592ab7e0","error":"1008:Unable to delete meshsync controllerconfigmaps \"meshery-nats-config\" not found","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.20.0/pkg/internal/controller/controller.go:332\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.20.0/pkg/internal/controller/controller.go:279\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.20.0/pkg/internal/controller/controller.go:240"}
Attempts to install using Meshery by deleting the Kubernetes connection and re-uploading kubeconfig failed to see a new Meshery Operator deployed. So, Meshery Operator was uninstall and reinstalled using helm
On boot of MeshSync, the following log is seen.
Logs
$ kubectl logs meshery-meshsync-64fb7cc66f-dxdzn -n meshery
time="2025-06-04T18:05:28Z" level=warning msg="Missing or outdated CRD. " app=meshsync code=1000 probable-cause="Missing or outdated CRD." severity=2 short-description="Error while initializing MeshSync configuration. .unable to update MeshSync configuration" suggested-remediation="Confirm that meshsyncs custom resource is present in the cluster."
time="2025-06-04T18:05:58Z" level=info msg="could not connect to broker: Get \"http://10.97.111.72:8222/connz\": dial tcp 10.97.111.72:8222: i/o timeout retrying..." app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Server started" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Pipeline started" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Listening for requests in: meshery.meshsync.request" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: local-database/ of kind: StorageClass" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1./ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: local-path/ of kind: StorageClass" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.acme.cert-manager.io/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.admissionregistration.k8s.io/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.apiextensions.k8s.io/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.apps/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.authentication.k8s.io/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.authorization.k8s.io/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.autoscaling/ of kind: APIService" app=meshsync
time="2025-06-04T18:05:59Z" level=info msg="Received ADD event for: v1.batch/ of kind: APIService" app=meshsync
and the following is a description of the MeshSync CRD that is installed in the cluster:
root@c3-medium-x86-03-meshery:~# kdes crd meshsync
Name: meshsyncs.meshery.io
Namespace:
Labels: <none>
Annotations: controller-gen.kubebuilder.io/version: v0.6.1
API Version: apiextensions.k8s.io/v1
Kind: CustomResourceDefinition
Metadata:
Creation Timestamp: 2025-04-23T19:22:10Z
Generation: 1
Resource Version: 84686274
UID: 3818b1e2-c660-4428-ac9b-83639182db23
Spec:
Conversion:
Strategy: None
Group: meshery.io
Names:
Kind: MeshSync
List Kind: MeshSyncList
Plural: meshsyncs
Singular: meshsync
Scope: Namespaced
Versions:
Name: v1alpha1
Schema:
openAPIV3Schema:
Description: MeshSync is the Schema for the meshsyncs API
Properties:
API Version:
Description: APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Type: string
Kind:
Description: Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Type: string
Metadata:
Type: object
Spec:
Description: MeshSyncSpec defines the desired state of MeshSync
Properties:
Broker:
Properties:
Custom:
Properties:
URL:
Description: This is the URL of an already running instance of the Broker, this is alternative to specifying the native configuration of the Broker instance
Type: string
Type: object
Native:
Properties:
Name:
Description: Name of the Broker instance to be deployed
Type: string
Namespace:
Description: Namespace within which the Broker instance to be deployed would run in
Type: string
Type: object
Type: object
Size:
Description: Desired replica count of the MeshSync instance, will be an integer value denoting the number of MeshSync instances that that should be in one cluster, currently only one instance of MeshSync is supported
Format: int32
Type: integer
Version:
Description: The current version of the Meshery application as from its release
Type: string
Watch - List:
Description: A ConfigMap that sets the resources e.g. pods,deployments and event types e.g. ADDED, MODIFIED… that the MeshSync instance tracks or ignores in the Kubernetes cluster
Properties:
Data:
Properties:
Blacklist:
Description: Blacklist resources are resources that the MeshSync should ignore its changes, More info: https://docs.meshery.io/reference/meshery-operator-crds#meshsync-crd-properties
Type: string
Whitelist:
Description: Whitelist resources are resources that the MeshSync should track its changes, More info: https://docs.meshery.io/reference/meshery-operator-crds#meshsync-crd-properties
Type: string
Type: object
Type: object
Type: object
Status:
Description: MeshSyncStatus defines the observed state of MeshSync
Properties:
Conditions:
Items:
Properties:
Last Probe Time:
Format: date-time
Type: string
Last Transition Time:
Format: date-time
Type: string
Message:
Type: string
Observed Generation:
Format: int64
Type: integer
Reason:
Type: string
Status:
Type: string
Type:
Type: string
Required:
lastTransitionTime
message
reason
status
type
Type: object
Type: array
Publishing - To:
Type: string
Type: object
Type: object
Served: true
Storage: true
Subresources:
Status:
Status:
Accepted Names:
Kind: MeshSync
List Kind: MeshSyncList
Plural: meshsyncs
Singular: meshsync
Conditions:
Last Transition Time: 2025-04-23T19:22:10Z
Message: no conflicts found
Reason: NoConflicts
Status: True
Type: NamesAccepted
Last Transition Time: 2025-04-23T19:22:10Z
Message: the initial names have been accepted
Reason: InitialNamesAccepted
Status: True
Type: Established
Stored Versions:
v1alpha1
Events: <none>
Contributor Resources
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.
- See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
- See Meshery site designs in Figma (open invite).
- Fill-in a Community Member Form and join the Community Slack for access.