busy-country-65143
11/17/2022, 8:54 AMambitious-dusk-59039
11/17/2022, 12:16 PMFetching releases from <https://api.github.com/repos/k3s-io/k3s/releases?per_page=100> -> AuthorizedOnly
I figured out a way to establish connectivity on other WSL distros:
On the windows host, there is a local Proxy server running on port 8887,
and I have a shell script which determines the right Network Interface and IP Addresses and sets the variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY accordingly to route all traffic from the wsl guest machine through this local proxy server which cares for Authentication.
This works fine with and without VPN in our corporate network and from remote work locations.
Now, I would like to:
*let Rancher Desktop (Windows executables) point to localhost:8887 as proxy Server
*let Rancher WSL Distros set HTTPS_PROXY, HTTP_PROXY, NO_PROXY via that shell script which picks the right network interface to determine the current IP Address
How could this be achieved?bland-translator-58922
11/17/2022, 1:04 PMflat-translator-32204
11/17/2022, 4:51 PMwget: unable to resolve host address
however upon logging onto that pod and trying to ping 8.8.8.8, the packets are being transmitted successfully.
bash-4.3# ping <http://google.com|google.com>
ping: bad address '<http://google.com|google.com>'
bash-4.3# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=49 time=1.133 ms
64 bytes from 8.8.8.8: seq=1 ttl=49 time=1.084 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.083/1.109/1.137 ms
bash-4.3#
Note:
1. Security groups are proper with access to all http traffic.
So I am not sure why the DNS resolution is failing on the EC2 instances.
I have tried restarting coredns service sudo kubectl -n kube-system rollout restart deployment coredns
and it temporarily fixes the issue but when I delete and recreate the pod, I again see issue with DNS resolution.
Please let me know of there is anything needs to be changed in config files or is there any setup issue.blue-needle-61113
11/17/2022, 7:34 PMgifted-breakfast-73755
11/17/2022, 10:14 PM2022/11/17 22:09:38 [ERROR] cluster [c-jpmvb] provisioning: [[network] Host [10.10.50.53] is not able to connect to the following ports: [10.10.50.44:2379]. Please check network policies and firewall rules]
https://github.com/rancher/rancher/issues/14249#issuecomment-1319249541gifted-breakfast-73755
11/17/2022, 10:15 PMetcd
node on port 22 but not on port 2379, yet I can telnet 10.10.50.44 2379
from the etcd
node itself (10.10.50.44
)quaint-rose-98687
11/17/2022, 11:18 PMhelm install rancher rancher-latest/rancher \
--namespace cattle-system \
--replicas=3 \
--set hostname=<http://mydomain.com|mydomain.com> \
--set tls=external
If been trying to figure this out for weeks 😞great-egg-9736
11/18/2022, 2:05 AMk3d cluster create --api-port 6550 -p "8081:80@loadbalancer" --agents 3
but how can I have multiple port mapping to use ingress to handle multiple k8s services/apps?
I would like to do something like
k3d cluster create --api-port 6550 -p "7001-7001:8081-80@loadbalancer" --agents 3
is that possible?breezy-ram-80329
11/18/2022, 3:45 AMadventurous-magazine-13224
11/18/2022, 7:10 AMsilly-jordan-81965
11/18/2022, 8:58 AMimportant-toddler-21468
11/18/2022, 9:41 AMminiature-kangaroo-6093
11/18/2022, 10:20 AMechoing-helmet-91774
11/18/2022, 11:28 AMastonishing-glass-5106
11/18/2022, 3:39 PMastonishing-glass-5106
11/18/2022, 3:45 PMhappy-elephant-46487
11/18/2022, 5:46 PMcareful-article-61190
11/19/2022, 1:39 AMagreeable-pager-80720
11/20/2022, 9:59 AMkubectl
with a downstream cluster.
I have fetched the kubeconfig with rancher cli: rancher clusters kubeconfig CLUSTER-ID CLUSTER-NAME > kubeconfig
kubectl
commands fail with Unable to connect to the server: x509: certificate signed by unknown authority
where should I look into to find the problem? which certificate is it talking about?
is this related to the contents of clusters.*.cluster.certificate-authority-data
in the kubeconfig file?polite-king-74071
11/20/2022, 4:20 PMpolite-king-74071
11/20/2022, 4:21 PMpolite-king-74071
11/20/2022, 4:22 PMwide-gold-24295
11/20/2022, 5:31 PMwide-gold-24295
11/20/2022, 5:32 PMwide-gold-24295
11/20/2022, 5:32 PMwide-gold-24295
11/20/2022, 5:33 PM[rancher@bb-rancheros ~]$ docker volume create --name bitbucketVolume
bitbucketVolume
[rancher@bb-rancheros ~]$ docker run -v bitbucketVolume:/var/atlassian/application-data/bitbucket -p 7990:7990 -p 7999:7999 atlassian/bitbucket
WARNING:root:######################################################################
WARNING:root:Starting Bitbucket with embedded search service. Note that this is
not a recommended configuration and is known to have issues with
clean shutdown. Ideally OpenSearch (previously Elasticsearch) should
be started in a separate container/pod.
WARNING:root:######################################################################
INFO:root:User is currently root. Will downgrade run user to bitbucket
INFO:root:Running Bitbucket with command '/opt/atlassian/bitbucket/bin/start-bitbucket.sh', arguments ['/opt/atlassian/bitbucket/bin/start-bitbucket.sh', '-fg']
The JRE_HOME environment variable is not defined correctly
This environment variable is needed to run this program
Edit set-jre-home.sh and define JRE_HOME
Startup has been aborted
[rancher@bb-rancheros ~]$
bland-translator-58922
11/21/2022, 9:21 AMmost-holiday-75301
11/21/2022, 9:22 AMCATTLE_UI_PRIMARY_COLOR
environment variable isn't supposed to change the --primary
CSS var? Although in /v3/settings/ui-primary-color
it looks set, no actual color change happens (Rancher v2.6.8).breezy-ram-80329
11/21/2022, 1:18 PM