Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What troubleshooting steps should I take when segment is not showing #21

Open
tigerinus opened this issue May 22, 2020 · 4 comments
Open

Comments

@tigerinus
Copy link

I believe I've followed all the steps correctly. However segment is not showing in either shell or tmux.

I can verify that the powerline_kubernetes module works fine individually:

Python 3.7.3 (default, Dec 20 2019, 18:57:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import powerline_kubernetes
>>> s = powerline_kubernetes.segments.KubernetesSegment()
>>> s.config['clusters'][0]['name']
'minikube'
>>>

Here is my themes/tmux/default.json:

{
    "segments": {
        "left": [
            {
                "function": "powerline_gitstatus.gitstatus"
            }
        ],
        "right": [
            {
                "function": "powerline.segments.common.sys.cpu_load_percent",
                "args": {
                    "interval": 5
                }
            },
            {
                "function": "powerline_docker.docker"
            },
            {
                "function": "powerline_kubernetes.kubernetes",
                "args": {
                    "show_kube_logo": true,
                    "show_cluster": true,
                    "show_namespace": true,
                    "show_default_namespace": false,
                    "alerts": [
                        "prod"
                    ]
                }
            },
            {
                "function": "powerline.segments.common.net.hostname"
            }
        ]
    }
}

I did add following lines to the corresponding colorscheme file (tried both colorscheme/default.json and colorscheme/tmux/default.json):

        "kubernetes":                 { "fg": "yellow",          "bg": "darkblue", "attrs": [] },
        "kubernetes:divider":         { "fg": "gray4",           "bg": "darkblue", "attrs": [] },
        "kubernetes_cluster":         { "fg": "gray10", "bg": "darkestblue", "attrs": [] },
        "kubernetes_cluster:alert":   { "fg": "gray10", "bg": "darkestred",  "attrs": [] },
        "kubernetes_namespace":       { "fg": "gray10", "bg": "darkestblue", "attrs": [] },
        "kubernetes_namespace:alert": { "fg": "gray10", "bg": "darkred",     "attrs": [] },

BTW, powerline_docker works for me fine.

Please help. Thanks!

@bigornoo
Copy link

Same problem for me. MacOS 10.14.6.

@tigerinus
Copy link
Author

I just realized it does not work for only minikube default context. It does work for a regular k8s context.

@Smirl
Copy link

Smirl commented Jul 16, 2020

I just ran into issues getting this set up. Turns out I had multiple kubeconfig files in my KUBECONFIG. Fixed in this issue #17

I debugged this by running the powerline-daemon in the foreground with:

powerline-daemon --foreground --replace

Hope this helps you figure out the issue.

@narthollis
Copy link

For me when it wasn't showing the issue was #13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants