gentle-dream-1571
08/12/2022, 2:11 PMmaster
only to get tons of unresolved modules when starting the new application with only the `shell`in it. It seems that the shell
is referencing components that have been moved out of the ./shell
and into `./pkg/rancher-components`that it is unable to resolve. For example:
ERROR in ./node_modules/@rancher/shell/components/RelatedResources.vue?vue&type=script&lang=js& (./node_modules/cache-loader/dist/cjs.js??ref--6-0!./node_modules/thread-loader/dist/cjs.js??ref--6-1!./node_modules/babel-loader/lib??ref--6-2!./node_modules/vue-loader/lib??vue-loader-options!./node_modules/@rancher/shell/components/RelatedResources.vue?vue&type=script&lang=js&)
Module not found: Error: Can't resolve '@components/BadgeState' in '/Users/rpatrick/Projects/research/verrazzano-dashboard/node_modules/@rancher/shell/components'
Any idea how to get past these issues?big-engine-23729
08/14/2022, 6:19 PMenough-xylophone-4568
08/27/2022, 4:36 PMstale-dinner-99388
08/31/2022, 5:47 AMmost-sunset-36476
09/06/2022, 8:16 AMstale-dinner-99388
09/09/2022, 12:56 PMhelm upgrade --install rancher rancher-latest/rancher --namespace cattle-system --set hostname=url --set ingress.tls.source="letsEncrypt" --set bootstrapPassword=abcdxyz --set letsEncrypt.email="email" --set letsEncrypt.environment="production"
gentle-dream-1571
09/09/2022, 2:41 PMloadCluster
action defined in the store to switch the currentCluster
but it seems to require a lot of information that we do not have readily available. Is this the right path or is there a better way?modern-piano-42327
09/12/2022, 2:52 PMdocker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher
Rancher Docker container is unable to start
Logs : -
INFO: Running k3s server --cluster-init --cluster-reset
2022/09/12 05:05:08 [INFO] Rancher version v2.6.8 (f650ce839) is starting
2022/09/12 05:05:08 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/09/12 05:05:08 [INFO] Listening on /tmp/log.sock
2022/09/12 05:05:08 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:10 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:12 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:14 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:16 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:18 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:20 [INFO] Waiting for server to become available: Get "<https://127.0.0.1:6444/version?timeout=15m0s>": dial tcp 127.0.0.1:6444: connect: connection refused
2022/09/12 05:05:28 [INFO] Running in single server mode, will not peer connections
2022/09/12 05:05:28 [INFO] Applying CRD <http://features.management.cattle.io|features.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://navlinks.ui.cattle.io|navlinks.ui.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusters.management.cattle.io|clusters.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://apiservices.management.cattle.io|apiservices.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusterregistrationtokens.management.cattle.io|clusterregistrationtokens.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://settings.management.cattle.io|settings.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://preferences.management.cattle.io|preferences.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://features.management.cattle.io|features.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusterrepos.catalog.cattle.io|clusterrepos.catalog.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://operations.catalog.cattle.io|operations.catalog.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://apps.catalog.cattle.io|apps.catalog.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://fleetworkspaces.management.cattle.io|fleetworkspaces.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://managedcharts.management.cattle.io|managedcharts.management.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusters.provisioning.cattle.io|clusters.provisioning.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://clusters.provisioning.cattle.io|clusters.provisioning.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://rkeclusters.rke.cattle.io|rkeclusters.rke.cattle.io>
2022/09/12 05:05:29 [INFO] Applying CRD <http://rkecontrolplanes.rke.cattle.io|rkecontrolplanes.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://rkebootstraps.rke.cattle.io|rkebootstraps.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://rkebootstraptemplates.rke.cattle.io|rkebootstraptemplates.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://rkecontrolplanes.rke.cattle.io|rkecontrolplanes.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://custommachines.rke.cattle.io|custommachines.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://etcdsnapshots.rke.cattle.io|etcdsnapshots.rke.cattle.io>
2022/09/12 05:05:30 [INFO] Applying CRD <http://clusters.cluster.x-k8s.io|clusters.cluster.x-k8s.io>
2022/09/12 05:05:30 [FATAL] k3s exited with: exit status 1
quick-eve-88192
09/13/2022, 2:32 PMsticky-artist-14452
09/28/2022, 5:26 AMmost-sunset-36476
09/28/2022, 5:23 PMstocky-account-63046
10/05/2022, 9:35 AM{vendor}
to the product name. The string that controls the names of built in repos are in catalog.repo.name
. You can just tweak those values to something more desirablequick-tiger-77531
10/06/2022, 11:42 AMgreat-oyster-72008
11/01/2022, 5:08 AMbrief-piano-55851
11/14/2022, 2:50 PMbrief-piano-55851
11/14/2022, 2:50 PMswift-table-42186
11/15/2022, 3:37 PMyarn install
and yarn dev
But I got errors
Do you have any ideas how can I fix it?numerous-apple-85303
11/16/2022, 12:42 PMswift-table-42186
11/18/2022, 9:11 AMswift-table-42186
11/30/2022, 9:40 AMfuture-alarm-92026
11/30/2022, 2:16 PMmeta/proxy
is happy about it
• I open a feature request for the rancher team to add Insecure TLS in their reverse proxy maybe could be on the same UI where whitelist for the driver are defined
• I do the code myself and I ask the Rancher team to approve the PR with insecure TSL support
• I do as a requirement to use the driver to have a valid cert in the Proxmox
• I make it so that to use the driver you have to somehow disable https to your Proxmox (do not want to do this for obvious reasons)future-alarm-92026
11/30/2022, 2:22 PMsalmon-carpenter-62625
12/02/2022, 2:27 PM- matchers:
name: severity
matchType: '=~'
value: 'warning|critical'
receiver: 'email'
continue: true
It seams there is some odd logic to transform this alertmanager-rancher-monitoring-alertmanager
secret, but this secret is not used by alertmanager, instead the another secret is created under the name alertmanager-rancher-monitoring-alertmanager-generated
but hit one is only cretead from the first one if the first one is somehow valid.
There is no error or anything like that but the content is like below:
route:
receiver: "null"
receivers:
- name: "null"
templates: []
If I use match like that:
- match:
alertname: CPUThrottlingHigh
receiver: email
then the generated secret is fine and I got my alert.
So is anyone here who know how this secret logic works about alerting, and can provide some example for using matchers as it seams its very unclear how to update it in proper way in rancher.quiet-house-51252
12/12/2022, 8:05 PMhappy-tent-70860
01/24/2023, 9:27 PMorange-airplane-98016
01/24/2023, 10:35 PMquiet-house-51252
01/25/2023, 3:34 PMgentle-dream-1571
02/22/2023, 4:40 PMquaint-candle-18606
03/06/2023, 10:58 PMwhite-xylophone-9961
03/10/2023, 2:05 PMFor this generation to compile you need to have some packages in your GOPATH:
* <http://github.com/go-openapi/runtime|github.com/go-openapi/runtime>
* <http://github.com/jessevdk/go-flags|github.com/jessevdk/go-flags>
You can get these now with: go get -u -f ./...
I'm not that familiar with golang, but I cloned the above two repos, and did
cd runtime
go install <http://github.com/go-openapi/runtime|github.com/go-openapi/runtime>
# wierd, no output
cd ../go-flags
go install <http://github.com/jessevdk/go-flags|github.com/jessevdk/go-flags>
# also no output
I rerun npm install
and get same missing package output.white-xylophone-9961
03/10/2023, 2:05 PMFor this generation to compile you need to have some packages in your GOPATH:
* <http://github.com/go-openapi/runtime|github.com/go-openapi/runtime>
* <http://github.com/jessevdk/go-flags|github.com/jessevdk/go-flags>
You can get these now with: go get -u -f ./...
I'm not that familiar with golang, but I cloned the above two repos, and did
cd runtime
go install <http://github.com/go-openapi/runtime|github.com/go-openapi/runtime>
# wierd, no output
cd ../go-flags
go install <http://github.com/jessevdk/go-flags|github.com/jessevdk/go-flags>
# also no output
I rerun npm install
and get same missing package output.