This project is mirrored from https://gitee.com/rancher/rancher.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 26 Mar, 2020 10 commits
-
-
Daishan authored
This commit moves data.json from dockerfile.dapper into scripts/package, also use COPY to avoid caching
-
kinarashah authored
Problem: This broke with a recent fix of moving when to increment node version for upgrade logic. If node version is not incremented, node plans won't get restored on rollback
-
Darren Shepherd authored
Fix panic in counts
-
Darren Shepherd authored
-
Darren Shepherd authored
-
rmweir authored
Update kontainer-engine
-
Ali Bazlamit authored
-
rmweir authored
-
Luther Monson authored
-
Brandon DePesa authored
-
- 25 Mar, 2020 8 commits
-
-
Darren Shepherd authored
Don't allow access to the local cluster if local cluster is not enabled
-
Darren Shepherd authored
-
Kinara Shah authored
planChanged only for upgraded nodes if cluster's upgrading
-
kinarashah authored
Problem: rke up triggers upgrade logic. If cluster's in upgrading state, plan will always change for nodes that haven't been upgraded yet. This will cause all upgraded nodes to cordon/drain & upgrade again. Solution: Skip nodes that haven't upgraded during plan change logic when cluster's upgrading.
-
Caleb Bron authored
adds istio images for 1.4.7
-
Sebastiaan van Steenis authored
Change frequent logs to TRACE
-
Sebastiaan van Steenis authored
-
rmweir authored
-
- 24 Mar, 2020 14 commits
-
-
Darren Shepherd authored
Remove constant log error
-
Darren Shepherd authored
-
Darren Shepherd authored
Fix memory leaks
-
Darren Shepherd authored
-
Caleb Bron authored
ROformatter
-
Westly Wright authored
-
Caleb Bron authored
-
Caleb Bron authored
-
Murali Paluru authored
-
Kinara Shah authored
increment cluster.Status.NodeVersion only on plan change
-
kinarashah authored
Problem: Current design is to increment node version of cluster status on every rke up. Deleting a node during upgrade also results into a rke up, and it causes all nodes to upgrade again because of mismatch between node and cluster's applied versions. Solution: change cluster.status.nodeversion only when plan changes on rke up
-
Sebastiaan van Steenis authored
-
loganhz authored
-
Caleb Bron authored
-
- 23 Mar, 2020 5 commits
-
-
Luther Monson authored
bumping rancher-machine version
-
Luther Monson authored
-
Westly Wright authored
-
Craig Jellick authored
Add all k3s images to airgap images
-
Dax McDonald authored
Previously, the UI would only list one node when it was being upgraded. Now the UI will show the top c nodes of the applying plan where c is equal to the concurrency
-
- 22 Mar, 2020 3 commits
-
-
Darren Shepherd authored
Add missing "create" verb and fix route for apps
-
Darren Shepherd authored
-
Darren Shepherd authored
-