question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make the Kubernetes Settings page more consistent when any setting changes

See original GitHub issue

Problem Description

Currently changes to some of the settings are deferred: a blue box appears at the bottom specifying that the cluster must be reset for the change to take effect. Others, namely the container-runtime and enable-k8s checkboxes, trigger a yes/no dialog box, and if the user chooses ‘yes’ the cluster is immediately reset.

The enable-traefik lives in its own world, involving neither the blue-box nor an immediate change.

All the changes should go through the delayed blue-box.

For one thing, it’s currently impossible to go in one step from (k8s-on, moby) to (k8s-off, containerd).

Proposed Solution

All desired changes in the K8s Settings page are reflected in the blue box at the bottom of the screen, and don’t take effect until the user either presses the “Reset Kubernetes” button or shuts the app down and restarts it.

Preflight Checklist

  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:1
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
ericpromislowcommented, Feb 24, 2022

+1 on the notification being out of the way and an unnoticeable color +1 on that this page shouldn’t have scroll bars

I’m not sure if we need a modal dialog to change these though. But changes should be additive (like switching engines and kubernetes on/off at the same time), and the UI should be consistent.

1reaction
rak-phillipcommented, Feb 23, 2022

I never liked the solution of using alerts at the bottom of the page or the pattern of Reseting Kubernetes to apply changes. I feel like this page has also grown to encompass more than just Kubernetes Settings… Perhaps, we can be more intentioned with our change and reintroduce our discussion of redesigning this section?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configuration Best Practices - Kubernetes
This document highlights and consolidates configuration best practices that are introduced throughout the user guide, Getting Started documentation, ...
Read more >
Configuration Drift in Kubernetes - What Is It and Why it Matters
Configuration drift is when running clusters in an environment become more different over time due to manual changes and updates on ...
Read more >
Kubernetes Hardening Guide
Periodically review all Kubernetes settings and use vulnerability scans to ensure risks are appropriately accounted for and security patches ...
Read more >
Best practices for running cost-optimized Kubernetes ...
This document discusses Google Kubernetes Engine (GKE) features and options, and the best practices for running cost-optimized applications ...
Read more >
What is Amazon EKS? - Amazon EKS - AWS Documentation
Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that you ... This secure and highly available configuration makes Amazon EKS reliable ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found