[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/afritzler/oopsie/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","afritzler","reponame","oopsie","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2020-05-02T09:49:55.190673Z","description","","is_private","last_updated","2021-07-27T05:53:09.210453Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",1644,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","

\n\n# oopsie\n\n $\"Gitter\"$

\n\n\n\nOopsie [/ˈuːpsi/] is a Kubernetes controller that watches all `Events` within a cluster and enriches failed objects with solutions found on [StackOverflow](https://stackoverflow.com) ([Github](https://github.com) and other sources coming soon).\n\n![recording](docs/images/recording.gif)\n\n## Why Oopsie?\n\nKubernetes is a great tool for orchestrating containerized workloads on a fleet of machines. Unfortunatelly, it is sometimes not that easy for new Kubernetes users to resolve problems which occur in their deployments. The illustration below is a visual representation of what happens when you deploy your first application after having mastered the [Wordpress and Guestbook examples](https://github.com/kubernetes/examples).\n\n

\n\nOopsie helps you, the people on Slack or community mailing lists, save time by answering questions to problems which already have been solved.\n\n## Usage\n\nYou can install oopsie with `GO111MODULE=\"on\" go get github.com/afritzler/oopsie`.\n\n__NOTE__: please use the latest go to do this, ideally go 1.13 or greater.\n\nThis will put `oopsie` in `$(go env GOPATH)/bin`. If you encounter the error `oopsie: command not found` after installation then you may need to either add that directory to your `$PATH` as shown [here](https://golang.org/doc/code.html#GOPATH) or do a manual installation by cloning the repo and run `make build` from the repository.\n\n```shell\nmkdir -p $GOPATH/src/github.com/afritzler && cd $GOPATH/src/github.com/afritzler/\ngit clone https://github.com/afritzler/oopsie.git\ncd oopsie\nmake build\n```\n\nAlternatively you can build the `oopsie` binary using a Docker container\n\n```shell\nmake docker-build\n```\n\nIn order to use `oopsie` you will need to point `KUBECONFIG` to the path `kubeconfig` of your Kubernetes cluster.\n\nIf you have a [kind](https://github.com/kubernetes-sigs/kind) based cluster running, you can set the `KUBECONFIG` prior to running `oopsie`.\n\n```shell\nexport KUBECONFIG=$(kind get kubeconfig-path)\n```\n\nFor [Minikube](https://github.com/kubernetes/minikube) based setup the `kubeconfig` is typically located under `~/.kube/config`.\n\nNow it's time to start the `oopsie` controller.\n\n```shell\noopsie\n```\n\nNow lets brake something by creating a broken deployment on our cluster.\n\n```shell\nkubectl apply -f https://raw.githubusercontent.com/afritzler/oopsie/master/examples/nginx-broken.yaml\n```\n\n`kubectl` should give us the follwing output\n\n```shell\nNAME READY STATUS RESTARTS AGE\nnginx-deployment-6b75cdff69-f6hkg 0/1 ErrImagePull 0 10s\n```\n\nIf we now look at the events of our broken pod\n\n```shell\nkubectl describe pod nginx-deployment-6b75cdff69-f6hkg\n```\n\nyou should see the following output\n\n```shell\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal Scheduled 8s default-scheduler Successfully assigned default/nginx-deployment-6b75cdff69-f6hkg to kind-control-plane\n Normal Pulling 7s kubelet, kind-control-plane Pulling image \"afritzler/nginx:1.17.6\"\n Warning Failed 5s kubelet, kind-control-plane Failed to pull image \"afritzler/nginx:1.17.6\": rpc error: code = Unknown desc = failed to resolve image \"docker.io/afritzler/nginx:1.17.6\": no available registry endpoint: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed\n Warning Failed 5s kubelet, kind-control-plane Error: ErrImagePull\n Normal BackOff 5s kubelet, kind-control-plane Back-off pulling image \"afritzler/nginx:1.17.6\"\n Warning Failed 5s kubelet, kind-control-plane Error: ImagePullBackOff\n Normal Hint 3s StackOverflow For error 'Error: ErrImagePull' I found something here -> https://stackoverflow.com/questions/48832017/minikube-error-errimagepull\n Normal Hint 3s StackOverflow For error 'Error: ImagePullBackOff' I found something here -> https://stackoverflow.com/questions/46002478/error-imagepullbackoff-when-scaling-working-deployment-kubernetes\n```\n\nFollow now the provided SackOverflow links which hopefully help you to resolve your issue. Since `oopsie` is observing all events inside your cluster you might also want to look into the events of other objects such as `node`, `pv`, etc.\n\n## Status and Future Work\n\nThis is the very first version of `oopsie` and currently only has one provider implemented to generate `hint` events. In the future I plan to look into the following topics:\n\n* Github provider to provide references to Github Issues\n* Use NLP techniques (tokenization/entity extraction) to improve search results\n* In-cluster operations documentation\n\n## Feedback and Support\n\nFeedback and contributions are always welcome! Feel free to open an [issue](https://github.com/afritzler/oopsie/issues) in case you hit any road bumps.\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",532398364,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",409723,"full_size",21480023,"id",99638980,"images",[97],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},"architecture","amd64","digest","sha256:be98b6b94d0499e915385e8059f7dd3609854d1808b05d23c1357fd76a33f1c1","features","last_pulled","2026-09-22T10:28:45.407977765Z","last_pushed","2021-07-27T05:53:09Z","os","linux","os_features","os_version","size","variant","2021-07-27T05:53:08.848404Z","last_updater","last_updater_username","media_type","latest","repository",8957044,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":11,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

afritzler/oopsie

Tags for afritzler/oopsie