Skip to content

issues Search Results · repo:GoogleContainerTools/kubehost language:Shell

Filter by

15 results
 (140 ms)

15 results

inGoogleContainerTools/kubehost (press backspace or delete to remove)

This issue was automatically created by Allstar. Security Policy Violation Security policy not enabled. A SECURITY.md file can give users information about what constitutes a vulnerability and how to ...
allstar
  • google-allstar-prod[bot]
  • 246
  • Opened 
    on Nov 7, 2023
  • #16

This issue was automatically created by Allstar. Security Policy Violation Found 1 outside collaborators with admin access. This policy requires users with this access to be members of the organisation. ...
allstar
  • google-allstar-prod[bot]
  • 246
  • Opened 
    on Nov 7, 2023
  • #15

This issue was automatically created by Allstar. Security Policy Violation No protection found for branch master !-- Edit section #updates -- !-- Current result text hash: c1d9df6acc17e8301cc3b999e50aaa3f511f42084d584457f4cb0744382958cd ...
allstar
  • google-allstar-prod[bot]
  • 246
  • Opened 
    on Nov 7, 2023
  • #14

This confused me as can be seen in #2 and #8. The last line of bind prints IP address only, I think it should print tue port as well.
  • ahmetb
  • Opened 
    on Oct 9, 2018
  • #13

kubehost has a documented limitation of only supporting services with a single port. Until this is addressed, we should output a warning message if a service is given that has multiple ports. Somewhere ...
enhancement
  • WilliamDenniss
  • Opened 
    on Oct 9, 2018
  • #12

Homebrew is a convenient package manager for OS X, would be great to have brew install kubehost, like the kubectx tools.
enhancement
  • WilliamDenniss
  • Opened 
    on Oct 9, 2018
  • #11

We should include the port in the success message Service exposed on ${ip}, to make it clear which port the service was exposed on. https://github.com/GoogleContainerTools/kubehost/blob/71d2a859cfba7172351200f2f0debb4d900c47e8/kubehost#L412 ...
enhancement
  • WilliamDenniss
  • 1
  • Opened 
    on Oct 9, 2018
  • #10

(As I stated in a previous issue, I expect kubehost to not to create a new deployment OR continuously mirror changes I make to my original deployment.) Problem I had a deployment/service that was kubehost ...
  • ahmetb
  • 1
  • Opened 
    on Oct 8, 2018
  • #9

I was basically playing with kubehost bind, and I had some services bind ed with that. Then I decided to nuke everything with kubectl delete deploy,service --all. Next time I brought up a sample container ...
  • ahmetb
  • 2
  • Opened 
    on Oct 8, 2018
  • #8

It seems like kubehost bind always binds to port 80. As far as I can tell, this prevents kubehost to be used with multiple exposed services at once (#2) as it tries to reuse port 80.
  • ahmetb
  • 1
  • Opened 
    on Oct 8, 2018
  • #7
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub